@100mslive/react-icons
[](https://github.com/100mslive/web-sdks/actions/workflows/lint-test-build.yml) [
| Version | Deps | Published |
|---|---|---|
| 0.12.2 | 0 / 3 | |
| 0.12.1 | 0 / 3 | |
| 0.12.0 | 0 / 3 | |
| 0.11.4 | 0 / 3 | |
| 0.11.3 | 0 / 3 | |
| 0.11.2 | 0 / 9 | |
| 0.11.1 | 0 / 9 | |
| 0.11.0 | 0 / 9 | |
| 0.10.39 | 0 / 9 | |
| 0.10.38 | 0 / 9 | |
| 0.10.37 | 0 / 9 | |
| 0.10.36 | 0 / 9 | |
| 0.10.35 | 0 / 9 | |
| 0.10.34 | 0 / 9 |
v0.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.