@bam.tech/danger-plugin-eslint

v2.2.1

See the lint, even for warnings

MIT
Latest version published 4 years ago
    npm install @bam.tech/danger-plugin-eslint
  

Package Health Score

40 / 100

Security

Security review needed
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
2.2.1 | 02/2018
Popular
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

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 @bam.tech/danger-plugin-eslint
Get started free

Popularity

Limited

Weekly Downloads (4)

Download trend
Dependents
0
GitHub Stars
15
Forks
0
Contributors
3

Direct Usage Popularity


The npm package @bam.tech/danger-plugin-eslint receives a total of 4 downloads a week. As such, we scored @bam.tech/danger-plugin-eslint popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @bam.tech/danger-plugin-eslint, we found that it has been starred 15 times, and that 0 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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
3
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like @bam.tech/danger-plugin-eslint is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 40/100 package health 40/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
4
Open PR
32
Last Release
4 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of @bam.tech/danger-plugin-eslint based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for @bam.tech/danger-plugin-eslint is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
>=8.0.0

Age
4 years
Dependencies
3 Direct
Versions
2
Install Size
13.4 kB
Dist-tags
1
# of Files
12
Maintainers
13
TS Typings
Yes

@bam.tech/danger-plugin-eslint 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.