[Best Practices] Dependency Vendoring at Scale

Learn pros & cons of "self-vendoring" Python, Perl, Ruby and other dependencies, and ways to secure and manage dependencies at scale.

View in browser   Hi David,   Development teams often settle for "self-vendoring" - the practice of including third-party source code directly into their product's codebase - as the "least worst" way to manage open source dependencies.   But resolving dependency conflicts and vulnerabilities can be a huge drain on developers, whose time is better spent creating new features and functionality.   Learn more about the challenges of self-vendoring for Python, Perl, Ruby and other languages, and best practices for managing and securing dependencies at scale. Get the White Paper Learn about: Pros and cons of self-vendoring Existing dependency management solutions Dependency vendoring best practices and managed distributions Reduce the burden on your development team! Dana Crane Product Marketing Manager, ActiveState ActiveState Software, 1000 - 1177 West Hastings Street, Vancouver, BC V6E 2K3 Unsubscribe Manage preferences