access-nyc-patterns

v0.8.0

User Interface Patterns for Benefits Access

GPL-3.0
Latest version published about 1 year ago
    npm install access-nyc-patterns
  
We couldn't find any similar packages Browse all packages

Package Health Score

42 / 100
  • Popularity
    Limited
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Limited

Popularity

Limited
Weekly Downloads (13)
Dependents
0
GitHub Stars
9
Forks
2
Contributors
3

The npm package access-nyc-patterns receives a total of 13 downloads a week. As such, we scored access-nyc-patterns popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package access-nyc-patterns, we found that it has been starred 9 times, and that 0 other projects on 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

No known security issues

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.4.0
0.5.4
0.6.1
0.7.0
0.8.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.4.0
0.5.4
0.6.1
0.7.0
0.8.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.4.0
0.5.4
0.6.1
0.7.0
0.8.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security Policy
No

Snyk detected that the latest version of access-nyc-patterns has a security vulnerability.

We highly advise you to review these security issues.

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

We found a way for you to contribute to the project! Looks like access-nyc-patterns is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test access-nyc-patterns
Fix it in your project with Snyk!

Maintenance

Inactive
deprecated
Commit Frequency
Open Issues
3
Merged PR
11
Open PR
4
Last Commit
18 days ago

Further analysis of the maintenance status of access-nyc-patterns 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 access-nyc-patterns 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Limited
Readme.md
No
Contributing.md
No
Code of Conduct
No
Contributors
3
Funding
No
License
GPL-3.0

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like access-nyc-patterns is missing a Code of Conduct.

We noticed that this project uses a license which requires less permissive conditions such as disclosing the source code, stating changes or redistributing the source under the same license. It is advised to further consult the license terms before use.


Embed Package Health Score Badge

package health: 42/100 package health 42/100

Package

Node.js Compatibility
not defined

Age
2 years
Dependencies
6 Direct / 6 Total
Versions
5
Install Size
144 MB
Dist-tags
1
# of Files
832
Maintainers
1
TS Typings
No

We detected a total of 6 direct & transitive dependencies for access-nyc-patterns. See the full dependency tree of access-nyc-patterns

access-nyc-patterns 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.