@steedos/ee_unpkg
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Enterprise fork of unpkg; README/metadata style is consistent across versions, not a phishing farm. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-import-meta | AI (phantom-deps): Framework-scoped Babel plugin loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-dynamic-import | AI (phantom-deps): Framework-scoped Babel plugin loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-class-properties | AI (phantom-deps): Framework-scoped Babel plugin loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-optional-chaining | AI (phantom-deps): Framework-scoped Babel plugin loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-export-default-from | AI (phantom-deps): Framework-scoped Babel plugin loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-export-namespace-from | AI (phantom-deps): Framework-scoped Babel plugin loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-nullish-coalescing-operator | AI (phantom-deps): Framework-scoped Babel plugin loaded by convention, not direct import. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 37 / 27 | |
| 3.0.1 | 38 / 27 | |
| 3.0.0 | 38 / 27 | |
| 1.1.1 | 38 / 27 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.