Third-Party Library

Definitions

1. A reusable code package developed and maintained by someone outside your organization, pulled in via a package manager (npm, pip, Maven, etc.) to avoid reimplementing common functionality like HTTP clients, date formatting, or authentication.

   In plain English: Pre-built code made by other people that you include in your project so you don't have to write everything from scratch.

   Example: "We depend on 1,200 third-party libraries and half of them haven't been updated in two years — time for an audit."

Related Terms

• SBOM
• Lock File
• Registry
• Upgrade
• Vendoring
• Open Source Supply Chain
• Package Security
• Transitive Dependency
• Outdated Dependency
• Left Pad