@dcg-overseas/polyhedron
Polyhedron (Prism & Pyramid) 3D visualization with Konva
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
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.6 | 0 / 9 | |
| 0.1.5 | 0 / 9 | |
| 0.1.2 | 0 / 9 | |
| 0.1.1 | 0 / 9 | |
| 0.1.0 | 0 / 9 |
v0.1.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (smileniuma001) than the most recent previously approved version (haoyouzhe) on 2026-06-04, but smileniuma001 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (haoyouzhe) than the most recent previously approved version (w88i817x902) on 2026-05-31, but haoyouzhe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.