cdn

v1.1.1

Upload your files to cdn.

MIT
Latest version published 7 years ago
    npm install cdn
  

Package Health Score

36 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Limited

Weekly Downloads (27)

Download trend
Dependents
3
GitHub Stars
16
Forks
3
Contributors
3

Direct Usage Popularity


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

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

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

07/2014
08/2014

Direct Vulnerabilities

1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.1.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular

License Risk

1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.1.1
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like cdn is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test cdn
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
3
Open PR
1
Last Release
7 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of cdn 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 cdn 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.

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 cdn is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 36/100 package health 36/100

Package

Node.js Compatibility
>= 0.10.0

Age
9 years
Dependencies
11 Direct
Versions
32
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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