eco

v1.1.0-rc-3

Embedded CoffeeScript templates

MIT
Latest version published 10 years ago
    npm install eco
  

Package Health Score

30 / 100

Security

Security issues found
Powered by Snyk
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.1.0-rc-3 | 12/2011
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.3 | 02/2011
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test eco
Get started free

Popularity

Small

Weekly Downloads (1,764)

Download trend
Dependents
197
GitHub Stars
1.73K
Forks
76
Contributors
3

Direct Usage Popularity

TOP 30%

The npm package eco receives a total of 1,764 downloads a week. As such, we scored eco popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package eco, we found that it has been starred 1,731 times, and that 197 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

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

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like eco is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 30/100 package health 30/100

Maintenance

Inactive
archived

Commit Frequency

No Recent Commits
Open Issues
25
Open PR
8
Last Release
10 years ago
Last Commit
10 years ago

Further analysis of the maintenance status of eco 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 eco 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
11 years
Dependencies
2 Direct
Versions
8
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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