@mml-io/3d-web-experience-server
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@mml-io/networked-dom-server | AI (dependencies): Sibling package in the same @mml-io org; consistent with the monorepo publishing pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package in a large monorepo; missing metadata is a style choice, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped org package with clear repo URL; missing description is a style issue, not a malice indicator. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 9 / 11 | |
| 0.27.1 | 9 / 11 | |
| 0.27.0 | 9 / 11 | |
| 0.26.1 | 8 / 6 | |
| 0.26.0 | 8 / 6 | |
| 0.25.0 | 8 / 6 | |
| 0.24.2 | 8 / 6 | |
| 0.24.1 | 8 / 6 | |
| 0.24.0 | 8 / 6 | |
| 0.23.4 | 8 / 6 | |
| 0.23.3 | 8 / 6 | |
| 0.23.2 | 8 / 6 | |
| 0.23.1 | 8 / 6 | |
| 0.23.0 | 8 / 6 |
v0.27.0
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 (marcuslongmuir) on 2026-03-18, 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.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.