@mml-io/3d-web-user-networking
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 3 / 14 | |
| 0.27.1 | 3 / 14 | |
| 0.27.0 | 3 / 14 | |
| 0.26.1 | 3 / 13 | |
| 0.26.0 | 3 / 13 | |
| 0.25.0 | 3 / 13 | |
| 0.24.2 | 3 / 13 | |
| 0.24.1 | 3 / 13 | |
| 0.24.0 | 3 / 13 | |
| 0.23.4 | 3 / 13 | |
| 0.23.3 | 3 / 13 | |
| 0.23.2 | 3 / 13 | |
| 0.23.1 | 3 / 13 | |
| 0.23.0 | 3 / 13 | |
| 0.22.0 | 1 / 6 |
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.27.0
1 findingPublished 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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.