danger

v11.1.1

Unit tests for Team Culture

MIT
Latest version published 1 month ago
    npm install danger
  
We couldn't find any similar packages Browse all packages

Package Health Score

95 / 100

Security

No known security issues
Powered by Snyk
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
11.1.1 | 07/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
11.0.7 | 05/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
10.9.0 | 01/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
9.4.0 | 03/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
9.3.0 | 03/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test danger
Get started free

Popularity

Influential project

Weekly Downloads (306,418)

Download trend
Dependents
505
GitHub Stars
4.55K
Forks
329
Contributors
190

Direct Usage Popularity

TOP 30%

The npm package danger receives a total of 306,418 downloads a week. As such, we scored danger popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package danger, we found that it has been starred 4,548 times, and that 505 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
190
Funding
Yes

A good and healthy external contribution signal for danger project, which invites more than one hundred open source maintainers to collaborate on the repository.

We found a way for you to contribute to the project! Looks like danger is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 95/100 package health 95/100

Maintenance

Healthy

Commit Frequency

Open Issues
139
Open PR
12
Last Release
1 month ago
Last Commit
11 days ago

Further analysis of the maintenance status of danger based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that danger demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=14.13.1

Age
6 years
Dependencies
37 Direct
Versions
299
Install Size
1.37 MB
Dist-tags
4
# of Files
373
Maintainers
3
TS Typings
Yes

danger has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.