What problem does it solve? Adopting a third-party library means trusting code you do not control, and teams often lack a systematic way to judge whether a dependency is maintained, secure, legally compatible, and worth its size cost before committing to it. ## Core Features & Use Cases - Health Signal Assessment: Evaluates commit frequency, issue response time, release cadence, bus factor, and community activity to predict whether a library will keep receiving fixes. - Security and License Auditing: Checks CVE databases, transitive dependency trees, copyleft versus permissive license obligations, lockfile integrity, and typosquatting risks. - Use Case: Before adding a new npm package to a commercial SaaS product, run this evaluation to confirm the license permits commercial use, scan for unpatched CVEs, measure bundle size impact, and produce a structured adopt/keep/replace recommendation. ## Quick Start Evaluate whether we should adopt the library 'some-package' for our project, covering maintenance health, security, license, and bundle size.