@myrmidon/gve-snapshot-rendition
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 | missing-githead | AI (provenance): Likely a CI/publish environment change; no other risk signals present and publisher has clean history. | ai | |
| source-diff | obfuscated-file:dist/src/layout/golden-layout-styles.d.ts | AI (source-diff): Long line is inlined CSS from golden-layout for Shadow DOM compatibility, explicitly documented in the file header. | ai | |
| phantom-deps | phantom-dep:fast-diff | AI (phantom-deps): Bundled library; dep inlined at build time. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build-time dep referenced in config; not a runtime import. | ai | |
| phantom-deps | phantom-dep:highlight.js | AI (phantom-deps): Bundled library; dep inlined at build time. | ai | |
| phantom-deps | phantom-dep:gsap | AI (phantom-deps): Bundled library; deps consumed at build time and inlined, not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:feather-icons | AI (phantom-deps): Bundled library; dep inlined at build time. | ai | |
| phantom-deps | phantom-dep:golden-layout | AI (phantom-deps): Bundled library; dep inlined at build time. | ai | |
| phantom-deps | phantom-dep:svg-pan-zoom | AI (phantom-deps): Bundled library; dep inlined at build time. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit TypeScript runtime dep; stable false positive for bundled packages. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 8 / 14 | |
| 2.0.3 | 8 / 14 | |
| 2.0.2 | 8 / 14 | |
| 2.0.1 | 8 / 14 | |
| 1.0.2 | 8 / 14 | |
| 1.0.1 | 8 / 14 | |
| 1.0.0 | 8 / 14 | |
| 0.0.8 | 8 / 14 |
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: myrmidon.
v2.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: myrmidon.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: myrmidon.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.