component

v1.1.0

Component package manager consuming git repositories

MIT
Latest version published 7 years ago
    npm install component
  

Package Health Score

47 / 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
1.1.0 | 03/2015
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.2 | 01/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.19.9 | 04/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.18.0 | 10/2013
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.17.6 | 09/2013
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 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 component
Get started free

Popularity

Recognized

Weekly Downloads (2,851)

Download trend
Dependents
343
GitHub Stars
4.58K
Forks
351
Contributors
50

Direct Usage Popularity

TOP 30%

The npm package component receives a total of 2,851 downloads a week. As such, we scored component popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package component, we found that it has been starred 4,582 times, and that 343 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
No
Contributors
50
Funding
No

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

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


Embed Package Health Score Badge

package health: 47/100 package health 47/100

Maintenance

Inactive
archived

Commit Frequency

No Recent Commits
Open Issues
33
Open PR
0
Last Release
7 years ago
Last Commit
4 years ago

Further analysis of the maintenance status of component 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 component 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
>= 0.10.0

Age
10 years
Dependencies
20 Direct
Versions
73
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
6
TS Typings
No

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