@istanbuljs/esm-loader-hook
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:babel-plugin-istanbul | AI (phantom-deps): Babel plugin loaded via config convention, not direct import; stable pattern. | ai | |
| phantom-deps | phantom-dep:@babel/preset-typescript | AI (phantom-deps): Babel preset loaded via config convention, not direct import; stable pattern. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-decorators | AI (phantom-deps): Babel plugin loaded via config convention, not direct import; stable pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 7 / 5 | |
| 0.2.0 | 5 / 6 | |
| 0.1.2 | 5 / 6 | |
| 0.1.1 | 5 / 6 | |
| 0.1.0 | 5 / 6 |
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.