@mml-io/3d-web-experience-client
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/3d-web-voice-chat | AI (dependencies): Sibling monorepo package from same publisher; version-locked to match this package. | ai | |
| dependencies | unvetted-dep:@mml-io/3d-web-text-chat | AI (dependencies): Sibling monorepo package from same publisher; version-locked to match this package. | ai | |
| dependencies | unvetted-dep:@mml-io/3d-web-avatar-selection-ui | AI (dependencies): Sibling monorepo package from same publisher; version-locked to match this package. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance present; stable positive signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance; consistent with org-level automation adoption. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is a cosmetic issue, not a spam/malware indicator for this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package with clear naming convention; missing description is cosmetic, not a malware signal. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 5 / 7 | |
| 0.27.1 | 5 / 7 | |
| 0.27.0 | 5 / 7 | |
| 0.26.1 | 6 / 5 | |
| 0.26.0 | 6 / 5 | |
| 0.25.0 | 6 / 5 | |
| 0.24.2 | 6 / 5 | |
| 0.24.1 | 6 / 5 | |
| 0.24.0 | 6 / 5 | |
| 0.23.4 | 6 / 5 | |
| 0.23.3 | 6 / 5 | |
| 0.23.2 | 6 / 5 | |
| 0.23.1 | 6 / 5 | |
| 0.23.0 | 6 / 5 | |
| 0.22.0 | 7 / 2 |
v0.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.27.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.27.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3
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.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.