@parcel/types-internal
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
Versions (showing 38 of 38)
| 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.16.5-canary.3498 | 4 / 0 | |
| 2.16.4-canary.3496 | 4 / 0 | |
| 2.16.2-canary.3489 | 4 / 0 | |
| 2.16.1-canary.3487 | 4 / 0 | |
| 2.16.1-canary.3486 | 4 / 0 | |
| 2.15.5-canary.3484 | 4 / 0 | |
| 2.15.5-canary.3483 | 4 / 0 | |
| 2.15.3-canary.3476 | 4 / 0 | |
| 2.15.3-canary.3473 | 4 / 0 | |
| 2.15.3-canary.3472 | 4 / 0 | |
| 2.15.2-canary.3465 | 4 / 0 | |
| 2.15.2-canary.3460 | 4 / 0 | |
| 2.15.2-canary.3458 | 4 / 0 | |
| 2.15.1-canary.3456 | 4 / 0 | |
| 2.15.1-canary.3455 | 4 / 0 | |
| 2.14.5-canary.3449 | 4 / 0 | |
| 2.14.5-canary.3443 | 4 / 0 | |
| 2.14.5-canary.3442 | 4 / 0 | |
| 2.14.5-canary.3441 | 4 / 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.4
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.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
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.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.