traceur 0.0.32
Experimental ES6 to ES5 compiler
traceur@0.0.32 was published on 2014-03-25. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.
All traceur versions · Permanent reference to 0.0.32 · View npm registry JSON · Latest release
Package specifications
| Version | 0.0.32 |
|---|---|
| License declaration | Apache License 2.0 |
| Published | 2014-03-25T23:00:44.507Z |
| Node.js requirement | >=0.10 |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./src/node/api.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 10 |
| Repository stars | 8124 |
| Repository forks | 566 |
Install traceur 0.0.32
npm install traceur@0.0.32 pnpm add traceur@0.0.32 yarn add traceur@0.0.32
Runtime dependencies
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- collections@0.2.2 — indirect
- commander@15.0.0 — direct
- mime@1.2.11 — indirect
- mimeparse@0.1.4 — indirect
- q@0.9.7 — indirect
- q-io@1.10.9 — direct
- qs@0.1.0 — indirect
- semver@7.8.5 — direct
- url2@0.0.0 — indirect
- weak-map@1.0.0 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — project is archived |
|---|---|
| Code-Review | 1/10 — Found 4/30 approved changesets -- score normalized to 1 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| License | 10/10 — license file detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Security-Policy | 10/10 — security policy file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Fuzzing | 0/10 — project is not fuzzed |
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-02T06:30:42.660Z
- https://api.deps.dev/v3/projects/github.com%2Fgoogle%2Ftraceur-compiler — retrieved 2026-11-02T06:24:01.205Z
- https://api.deps.dev/v3/systems/npm/packages/traceur/versions/0.0.32 — retrieved 2026-11-02T06:30:43.054Z
- https://api.deps.dev/v3/systems/npm/packages/traceur/versions/0.0.32:dependencies — retrieved 2026-11-02T06:30:43.083Z