grunt-env

v1.0.1

Specify an ENV configuration for future tasks in the chain For more information about how to use this package see README

Latest version published 3 years ago
License: Unrecognized

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

57 / 100

Explore Similar Packages

Security

No known security issues
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.0.1 | 07/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.4.4 | 02/2015
Popular
  • 0
    H
  • 0
    M
  • 0
    L
0.3.0 | 04/2013
  • 0
    H
  • 0
    M
  • 0
    L
0.2.1 | 02/2013
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.0 | 10/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Unrecognized
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

Recognized

Weekly Downloads (25,570)

Download trend
Dependents
869
GitHub Stars
223
Forks
40
Contributors
20

Direct Usage Popularity

TOP 10%

The npm package grunt-env receives a total of 25,570 downloads a week. As such, we scored grunt-env popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package grunt-env, we found that it has been starred 223 times, and that 869 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.

Community

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

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


Embed Package Health Score Badge

package health: 57/100 package health 57/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
7
Open PR
2
Last Release
3 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of grunt-env 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 grunt-env 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
*

Age
10 years
Dependencies
2 Direct
Versions
12
Install Size
15.3 kB
Dist-tags
1
# of Files
7
Maintainers
2
TS Typings
No

grunt-env 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.