@parcel/runtime-js
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/helpers/browser/esm-js-loader-retry.js | AI (source-diff): File is Babel-transpiled/minified browser helper code (regenerator-runtime, typeof helpers) — standard build output for a bundler runtime package. Not obfuscation. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is the expected mechanism for Parcel's JS runtime loader to execute bundled code in Node.js; inherent to a bundler's design. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require() by resolved file path is the core function of Parcel's node-loader helper; expected and benign for a bundler runtime. | ai | |
| phantom-deps | phantom-dep:@parcel/diagnostic | AI (phantom-deps): Same-org @parcel/diagnostic dependency; phantom detection likely reflects indirect usage within the monorepo. Not a concern. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 2.16.4 | 4 / 0 | |
| 2.16.3 | 4 / 0 | |
| 2.16.2 | 4 / 0 | |
| 2.16.1 | 4 / 0 | |
| 2.16.0 | 4 / 0 | |
| 2.15.4 | 4 / 0 | |
| 2.15.3 | 4 / 0 | |
| 2.15.2 | 4 / 0 | |
| 2.15.1 | 4 / 0 | |
| 2.15.0 | 4 / 0 | |
| 2.14.4 | 4 / 0 | |
| 2.14.3 | 4 / 0 | |
| 2.14.2 | 4 / 0 | |
| 2.14.1 | 4 / 0 | |
| 2.14.0 | 4 / 0 | |
| 2.13.3 | 4 / 0 | |
| 2.13.2 | 4 / 0 | |
| 2.13.1 | 4 / 0 | |
| 2.13.0 | 4 / 0 | |
| 2.12.0 | 4 / 0 | |
| 2.11.0 | 4 / 0 | |
| 2.10.3 | 4 / 0 | |
| 2.10.2 | 4 / 0 | |
| 2.10.1 | 4 / 0 | |
| 2.10.0 | 4 / 0 | |
| 2.9.3 | 4 / 0 | |
| 2.9.2 | 4 / 0 | |
| 2.9.1 | 4 / 0 | |
| 2.9.0 | 4 / 0 | |
| 2.8.3 | 3 / 0 | |
| 2.8.2 | 3 / 0 | |
| 2.8.1 | 3 / 0 | |
| 2.8.0 | 3 / 0 | |
| 2.7.0 | 3 / 0 | |
| 2.6.2 | 3 / 0 | |
| 2.6.1 | 3 / 0 | |
| 2.6.0 | 3 / 0 | |
| 2.5.0 | 3 / 0 | |
| 2.4.1 | 3 / 0 | |
| 2.4.0 | 3 / 0 | |
| 2.3.2 | 3 / 0 | |
| 2.3.1 | 3 / 0 | |
| 2.3.0 | 3 / 0 | |
| 2.2.1 | 3 / 0 | |
| 2.2.0 | 3 / 0 | |
| 2.1.1 | 3 / 0 | |
| 2.1.0 | 3 / 0 | |
| 2.0.1 | 3 / 0 | |
| 2.0.0 | 3 / 0 |
v2.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.