@100mslive/hms-whiteboard
[](https://github.com/100mslive/web-sdks/actions/workflows/lint-test-build.yml) [: Transition to GitHub Actions CI publishing with SLSA attestation; consistent with org-level automation adoption. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.2.2 | 4 / 11 | |
| 0.2.1 | 4 / 11 | |
| 0.2.0 | 4 / 11 | |
| 0.1.4 | 4 / 11 | |
| 0.1.3 | 4 / 11 | |
| 0.1.2 | 4 / 19 | |
| 0.1.1 | 4 / 19 | |
| 0.1.0 | 4 / 19 | |
| 0.0.29 | 4 / 19 | |
| 0.0.28 | 4 / 19 | |
| 0.0.27 | 4 / 19 | |
| 0.0.26 | 4 / 19 | |
| 0.0.25 | 4 / 19 | |
| 0.0.24 | 4 / 19 |
v0.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. 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.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-19. 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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.