scandal

v3.2.0

Directory Search and Scan Utilities

MIT
Latest version published 3 years ago
    npm install scandal
  
We couldn't find any similar packages Browse all packages

Package Health Score

46 / 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
3.2.0 | 06/2019
Popular
  • 0
    H
  • 0
    M
  • 0
    L
3.1.0 | 03/2017
  • 0
    H
  • 0
    M
  • 0
    L
2.3.0 | 03/2017
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0 | 01/2015
  • 0
    H
  • 0
    M
  • 0
    L
1.0.3 | 10/2014
  • 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 scandal
Get started free

Popularity

Limited

Weekly Downloads (962)

Download trend
Dependents
1
GitHub Stars
39
Forks
32
Contributors
20

Direct Usage Popularity

TOP 5%

The npm package scandal receives a total of 962 downloads a week. As such, we scored scandal popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package scandal, we found that it has been starred 39 times, and that 1 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

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
Yes
Contributors
20
Funding
No

With more than 10 contributors for the scandal repository, this is possibly a sign for a growing and inviting community.


Embed Package Health Score Badge

package health: 46/100 package health 46/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
5
Open PR
8
Last Release
3 years ago
Last Commit
1 year ago

Further analysis of the maintenance status of scandal 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 scandal 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
not defined

Age
9 years
Dependencies
6 Direct
Versions
46
Install Size
45.9 kB
Dist-tags
1
# of Files
13
Maintainers
10
TS Typings
No

scandal 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.