c9

v3.1.3534

Cloud9 Client For more information about how to use this package see README

Latest version published 8 years ago
License: Unrecognized

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

56 / 100

Explore Similar Packages

Security

No known security issues
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.1.3534 | 04/2017
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.2112 | 07/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.20 | 11/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Unrecognized
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.

Get started free

Popularity

Small

Weekly Downloads (132)

Download trend
GitHub Stars
2.56K
Forks
922
Contributors
60

Direct Usage Popularity


The npm package c9 receives a total of 132 downloads a week. As such, we scored c9 popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package c9, we found that it has been starred 2,564 times.

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
Yes
Contributors
60
Funding
No

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


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Maintenance

Inactive
archived

Commit Frequency

No Recent Commits
Open Issues
162
Open PR
18
Last Release
8 years ago
Last Commit
4 years ago

Further analysis of the maintenance status of c9 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 c9 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
12 years
Dependencies
0 Direct
Versions
43
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
4
TS Typings
No

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