@heejun/spa-seo-gateway-core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): pino-pretty is a legitimate runtime logging formatter; commonly declared as a dep without direct import in library code. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.9.0 | 19 / 4 | |
| 1.6.0 | 19 / 4 | |
| 1.5.0 | 17 / 2 | |
| 1.1.0 | 16 / 2 | |
| 1.0.0 | 16 / 2 |
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.