gulp-rename

v2.0.0

Rename files

MIT
Latest version published 1 year ago
    npm install gulp-rename
  
We couldn't find any similar packages Browse all packages

Package Health Score

70 / 100
Make sure the open source you're using is safe to use
Secure my Project

Popularity

Popular

Weekly Downloads (741,506)

Dependents
25.09K
GitHub Stars
677
Forks
73
Contributors
20

The npm package gulp-rename receives a total of 741,506 downloads a week. As such, we scored gulp-rename popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package gulp-rename, we found that it has been starred 677 times, and that 25,091 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.

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.1.0
0.2.2
1.4.0
2.0.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

Indirect Vulnerabilities

0.1.0
0.2.2
1.4.0
2.0.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

License Risks

0.1.0
0.2.2
1.4.0
2.0.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
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like gulp-rename is missing a security policy.


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

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test gulp-rename
Keep your project free of vulnerabilities with Snyk

Maintenance

Sustainable

Commit Frequency

No Recent Commits
Open Issues
3
Open PR
1
Last Release
1 year ago
Last Commit
1 year ago

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

An important project maintenance signal to consider for gulp-rename 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.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No

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


Embed Package Health Score Badge

package health: 70/100 package health 70/100

Package

Node.js Compatibility
>=4

Age
7 years
Dependencies
0 Direct
Versions
12
Install Size
7.17 kB
Dist-tags
1
# of Files
5
Maintainers
5
TS Typings
Yes

gulp-rename 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.