gscan

v4.43.1

Scans Ghost themes looking for errors, deprecations, features and compatibility For more information about how to use this package see README

Latest version published 1 month 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

73 / 100

Explore Similar Packages

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
4.43.1 | 05/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.42.1 | 04/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.34.0 | 08/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.6.1 | 12/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.11.0 | 10/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

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 (4,035)

Download trend
GitHub Stars
74
Forks
54
Contributors
50

Direct Usage Popularity

TOP 5%

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

Based on project statistics from the GitHub repository for the npm package gscan, we found that it has been starred 74 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
Yes

With more than 10 contributors for the gscan 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 gscan is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 73/100 package health 73/100

Maintenance

Healthy

Commit Frequency

Open Issues
22
Open PR
14
Last Release
1 month ago
Last Commit
11 days ago

Further analysis of the maintenance status of gscan based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that gscan 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.

Package

Node.js Compatibility
^14.18.0 || ^16.13.0 || ^18.12.1 || ^20.11.1

Age
8 years
Dependencies
22 Direct
Versions
202
Install Size
12 MB
Dist-tags
1
# of Files
125
Maintainers
30
TS Typings
No

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