traceur

v0.0.111

ES6 to ES5 compiler For more information about how to use this package see README

Latest version published 8 years ago
License: Apache-2.0

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

62 / 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
0.0.111 | 06/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.105 | 03/2016
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
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

Popular

Weekly Downloads (10,229)

Download trend
GitHub Stars
8.17K
Forks
581
Contributors
60

Direct Usage Popularity

TOP 10%

The npm package traceur receives a total of 10,229 downloads a week. As such, we scored traceur popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package traceur, we found that it has been starred 8,173 times.

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

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
60
Funding
No

With more than 10 contributors for the traceur repository, this is possibly a sign for a growing and inviting community.


Embed Package Health Score Badge

package health: 62/100 package health 62/100

Maintenance

Inactive

Commit Frequency

Open Issues
292
Open PR
1
Last Release
8 years ago
Last Commit
6 months ago

Further analysis of the maintenance status of traceur 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 traceur 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
>=0.10

Age
12 years
Dependencies
5 Direct
Versions
111
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
2
TS Typings
No

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