@100mslive/hms-video-store
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.14.2 | 9 / 8 | |
| 0.14.1 | 9 / 8 | |
| 0.14.0 | 9 / 8 | |
| 0.13.4 | 9 / 8 | |
| 0.13.3 | 9 / 8 | |
| 0.13.2 | 9 / 8 | |
| 0.13.1 | 9 / 8 | |
| 0.13.0 | 9 / 8 | |
| 0.12.39 | 9 / 8 | |
| 0.12.38 | 9 / 8 | |
| 0.12.37 | 9 / 8 | |
| 0.12.36 | 9 / 8 | |
| 0.12.35 | 9 / 8 | |
| 0.12.34 | 9 / 8 |
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.