@mlightcad/cad-simple-viewer
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.5.8 | 0 / 14 | |
| 1.5.3 | 0 / 13 | |
| 1.5.2 | 3 / 10 | |
| 1.5.0 | 3 / 8 | |
| 1.4.13 | 3 / 8 | |
| 1.4.12 | 3 / 8 | |
| 1.2.2 | 3 / 7 | |
| 1.0.14 | 2 / 6 | |
| 1.0.13 | 2 / 6 | |
| 1.0.12 | 2 / 6 | |
| 1.0.11 | 2 / 6 | |
| 1.0.10 | 2 / 6 | |
| 1.0.9 | 2 / 6 | |
| 1.0.7 | 2 / 6 | |
| 1.0.6 | 2 / 6 | |
| 1.0.5 | 2 / 6 | |
| 1.0.3 | 2 / 3 | |
| 1.0.2 | 2 / 3 | |
| 1.0.1 | 2 / 3 | |
| 1.0.0 | 2 / 3 |
v1.5.8
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (mlight.li) on 2026-07-19, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.