Disclaimer

Last updated: December 2024

Not a Substitute for Professional Security Assessment

DepShield is a tool to assist with vulnerability identification. It is not a substitute for professional security assessment, penetration testing, or comprehensive security audits.

Data Accuracy

Vulnerability data is sourced from third-party databases including OSV (Open Source Vulnerabilities) and CISA's Known Exploited Vulnerabilities catalog. While we strive for accuracy, we cannot guarantee that:

  • All vulnerabilities affecting your dependencies are detected
  • Reported vulnerabilities are applicable to your specific use case
  • CVSS scores and severity ratings are accurate or current
  • Recommended fixed versions resolve all security issues

Limitations

DepShield currently supports npm (Node.js) dependencies only. The Service:

  • Does not analyze source code for vulnerabilities
  • Does not detect vulnerabilities in private packages
  • Does not verify that vulnerabilities are exploitable in your context
  • Does not provide runtime protection or monitoring
  • May not include vulnerabilities published after the last database update

CISA KEV Interpretation

The presence of a vulnerability in CISA's Known Exploited Vulnerabilities catalog indicates confirmed exploitation in the wild, but:

  • It does not mean your specific application is being targeted
  • Remediation timelines apply to federal agencies and may not be mandatory for your organization
  • Not all exploited vulnerabilities appear in the KEV catalog

No Liability

DepShield and its operators are not liable for any damages arising from:

  • Security incidents that occur despite using our Service
  • Decisions made based on scan results
  • Incomplete or inaccurate vulnerability data
  • Service downtime or unavailability

Recommendations

We recommend:

  • Using DepShield as one component of a comprehensive security program
  • Verifying critical vulnerabilities through multiple sources
  • Consulting with security professionals for high-risk applications
  • Keeping dependencies updated as a general practice
  • Implementing defense-in-depth strategies beyond dependency management