1. Advisor
  2. JavaScript packages
  3. @pnpm/registry-mock

@pnpm/registry-mock

v3.43.0

Mock the npm registry For more information about how to use this package see README

Latest version published 26 days ago
License: MIT
NPM
GitHub

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

67 / 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
3.43.0 | 10/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.42.0 | 10/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.20.0 | 06/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.11.1 | 11/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.10.0 | 11/2019
  • 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

Small

Weekly Downloads (1,276)

Download trend
GitHub Stars
17
Forks
3
Contributors
6

Direct Usage Popularity

TOP 30%

The npm package @pnpm/registry-mock receives a total of 1,276 downloads a week. As such, we scored @pnpm/registry-mock popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @pnpm/registry-mock, we found that it has been starred 17 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
6
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like @pnpm/registry-mock is missing a Code of Conduct.

Embed Package Health Score Badge

package health: 67/100 package health 67/100

Maintenance

Healthy

Commit Frequency

Open Issues
0
Open PR
4
Last Release
26 days ago
Last Commit
26 days ago

Further analysis of the maintenance status of @pnpm/registry-mock based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @pnpm/registry-mock demonstrates a positive version release cadence with at least one new version released in the past 3 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
>=10.13
Age
5 years
Dependencies
8 Direct
Versions
106
Install Size
353 kB
Dist-tags
2
# of Files
456
Maintainers
2
TS Typings
No

@pnpm/registry-mock 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.