6to5-core
Turn ES6 code into readable vanilla ES5 with source maps
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:lib/6to5/api/browser.js | AI (source-diff): This file is the browser-side transpiler API for 6to5. XHR + new Function() is the documented mechanism for fetching and executing transpiled scripts in-browser — core functionality, not malware. | ai | |
| source-diff | net-exec-file:lib/6to5/helpers/to-fast-properties.js | AI (source-diff): The eval() is dead code (after a return statement) — a documented V8 fast-properties optimization trick from Bluebird. No network calls exist in this file; the HIGH finding is a false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in file.js resolves module formatters by name via util.resolve — standard plugin architecture for a transpiler, not arbitrary code loading. | ai | |
| bogus-package | bogus-package | AI (bogus-package): sebmck is Sebastian McKenzie, original author of 6to5/Babel. SPAM-FLAGGED is a false positive for this well-known developer. Package is legitimate with 4123 days of history. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() in to-fast-properties.js is an unreachable V8 fast-properties optimization hint after a return statement — a well-known legitimate pattern, not malicious. | ai | |
| phantom-deps | phantom-dep:roadrunner | AI (phantom-deps): roadrunner is a declared dependency used conditionally; not directly imported in main source but legitimately referenced in config. Expected for this transpiler. | ai | |
| phantom-deps | phantom-dep:useragent | AI (phantom-deps): useragent is a declared dependency used conditionally; not directly imported in main source but legitimately referenced in config. Expected for this transpiler. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in browser.js is the transpiler's browser runtime executing compiled ES6 code — core functionality of a transpiler, not a supply-chain risk. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 3.6.5 | 22 / 0 | |
| 3.6.4 | 22 / 0 | |
| 3.6.3 | 22 / 0 | |
| 3.6.2 | 22 / 0 | |
| 3.6.1 | 22 / 0 | |
| 3.6.0 | 22 / 0 | |
| 3.5.3 | 22 / 0 | |
| 3.5.2 | 22 / 0 | |
| 3.5.1 | 22 / 0 | |
| 3.5.0 | 22 / 0 | |
| 3.4.1 | 22 / 0 | |
| 3.4.0 | 22 / 0 | |
| 3.3.12 | 22 / 0 | |
| 3.3.11 | 22 / 0 | |
| 3.3.10 | 22 / 0 | |
| 3.3.9 | 22 / 0 | |
| 3.3.7 | 22 / 0 | |
| 3.3.5 | 22 / 0 | |
| 3.3.4 | 22 / 0 | |
| 3.3.3 | 22 / 0 | |
| 3.3.2 | 22 / 0 | |
| 3.3.1 | 22 / 0 | |
| 3.3.0 | 22 / 0 | |
| 3.2.1 | 22 / 0 | |
| 3.2.0 | 22 / 0 | |
| 3.1.1 | 22 / 0 | |
| 3.1.0 | 22 / 0 | |
| 3.0.16 | 22 / 0 | |
| 3.0.15 | 21 / 0 | |
| 3.0.14 | 21 / 0 | |
| 3.0.13 | 21 / 0 | |
| 3.0.12 | 21 / 0 | |
| 3.0.11 | 20 / 0 | |
| 3.0.10 | 20 / 0 | |
| 3.0.9 | 20 / 0 | |
| 3.0.8 | 20 / 0 | |
| 3.0.7 | 20 / 0 | |
| 3.0.6 | 20 / 0 | |
| 3.0.5 | 20 / 0 | |
| 3.0.4 | 20 / 0 | |
| 3.0.3 | 20 / 0 | |
| 3.0.2 | 20 / 0 | |
| 3.0.1 | 20 / 0 | |
| 3.0.0 | 20 / 0 | |
| 2.13.7 | 17 / 0 | |
| 2.13.3 | 17 / 0 | |
| 2.13.2 | 17 / 0 | |
| 2.13.1 | 17 / 0 | |
| 2.13.0 | 17 / 0 | |
| 2.12.6 | 17 / 0 | |
| 2.12.5 | 17 / 0 |
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.