@types/es-abstract
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/es-to-primitive | AI (dependencies): Sibling DefinitelyTyped package from the same trusted types publisher; normal type dependency pattern. | ai | |
| phantom-deps | phantom-dep:@types/is-callable | AI (phantom-deps): @types packages are loaded by TypeScript convention, not direct imports. Phantom dep finding is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/es-to-primitive | AI (phantom-deps): @types packages are loaded by TypeScript convention, not direct imports. Phantom dep finding is a stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.24.0 | 1 / 0 | |
| 1.17.10 | 1 / 0 | |
| 1.17.9 | 1 / 0 | |
| 1.17.8 | 1 / 0 | |
| 1.17.7 | 1 / 0 | |
| 1.17.6 | 1 / 0 | |
| 1.17.5 | 1 / 0 | |
| 1.17.4 | 1 / 0 | |
| 1.17.3 | 1 / 0 | |
| 1.17.2 | 1 / 0 | |
| 1.17.1 | 1 / 0 | |
| 1.17.0 | 1 / 0 | |
| 1.16.6 | 2 / 0 | |
| 1.16.5 | 2 / 0 | |
| 1.16.4 | 2 / 0 | |
| 1.16.3 | 2 / 0 | |
| 1.16.2 | 2 / 0 | |
| 1.16.1 | 2 / 0 | |
| 1.16.0 | 2 / 0 |
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.