@mml-io/mml-web-threejs
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; stable pattern for this org going forward. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package with SLSA provenance and 101 versions; thin README/no keywords is a cosmetic pattern for this org. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.26.1 | 2 / 4 | |
| 0.26.0 | 2 / 4 | |
| 0.25.0 | 2 / 4 | |
| 0.24.1 | 2 / 4 | |
| 0.24.0 | 2 / 4 | |
| 0.23.1 | 2 / 2 | |
| 0.23.0 | 2 / 2 | |
| 0.22.0 | 2 / 2 | |
| 0.21.3 | 2 / 2 | |
| 0.21.2 | 2 / 2 | |
| 0.21.1 | 2 / 2 | |
| 0.21.0 | 2 / 2 | |
| 0.20.0 | 2 / 2 | |
| 0.19.7 | 2 / 2 | |
| 0.19.6 | 2 / 2 | |
| 0.19.5 | 2 / 2 | |
| 0.19.4 | 2 / 2 | |
| 0.19.3 | 2 / 2 | |
| 0.19.2 | 2 / 2 | |
| 0.19.1 | 2 / 2 | |
| 0.19.0 | 2 / 2 |
v0.19.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.