@glimmer/component

v1.1.2

Glimmer component library For more information about how to use this package see README

Latest version published 2 years ago
License: MIT

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

53 / 100

Security

Security review needed
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.2 | 04/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.4 | 02/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.13.0 | 11/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.12.0 | 09/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.11.1 | 09/2018
  • 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.

Get started free

Popularity

Popular

Weekly Downloads (134,443)

Download trend
GitHub Stars
746
Forks
75
Contributors
50

Direct Usage Popularity

TOP 5%

The npm package @glimmer/component receives a total of 134,443 downloads a week. As such, we scored @glimmer/component popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @glimmer/component, we found that it has been starred 746 times.

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 @glimmer/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 @glimmer/component is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
29
Open PR
14
Last Release
2 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of @glimmer/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 @glimmer/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
6

Age
7 years
Dependencies
14 Direct
Versions
95
Install Size
222 kB
Dist-tags
2
# of Files
55
Maintainers
14
TS Typings
Yes

@glimmer/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.