Is Danger Safe?

Danger — Nerq Trust Score 65.1/100 (B- grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-03-31.

Use Danger with some caution. Danger is a Node.js package with a Nerq Trust Score of 65.1/100 (B-), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 80/100. Popularity: 68/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-31. Machine-readable data (JSON).

Is Danger safe?

CAUTION — Danger has a Nerq Trust Score of 65.1/100 (B-). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.

Security Analysis → {name} Privacy Report →

What is Danger's trust score?

Danger has a Nerq Trust Score of 65.1/100, earning a B- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
80
Popularity
68

What are the key security findings for Danger?

Danger's strongest signal is security at 80/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Security score: 80/100 (strong)
Popularity: 68/100 — community adoption

What is Danger and who maintains it?

Authormacklinu
Categorynpm
SourceN/A

Danger Across Platforms

Same developer/company in other registries:

danger
56/100 · gems
danger
35/100 · crates

Similar Npm by Trust Score

babel-plugin-jest-hoist (74)@smithy/util-stream (74)@aws-sdk/middleware-bucket-endpoint (74)@aws-sdk/middleware-ssec (74)@aws-sdk/middleware-location-constraint (74)
See all safest Npm →

Safety Guide: Danger

What is Danger?

Danger is a Node.js package — Unit tests for Team Culture.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=danger

Key Safety Concerns for Node.js packages

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Trust Assessment

Danger has a Nerq Trust Score of 65/100 (B-) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Danger safe to use?
Use with some caution. danger has a Nerq Trust Score of 65.1/100 (B-). Strongest signal: security (80/100). Score based on security (80/100), popularity (68/100).
What is Danger's trust score?
danger: 65.1/100 (B-). Score based on: security (80/100), popularity (68/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=danger
What are safer alternatives to Danger?
In the npm category, more Node.js packages are being analyzed — check back soon. danger scores 65.1/100.
Does Danger have known vulnerabilities?
Nerq checks Danger against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 80/100. Run your package manager's audit command for the latest findings.
How actively maintained is Danger?
Danger has a trust score of 65.1/100 (B-). Below Nerq Verified threshold — conduct additional review.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy Policy