@fluentui-react-native/spinner
A cross-platform Fluent spinner component
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo release tooling; publisher has long clean track record. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party sibling package in same monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft OSS monorepo package published via bot; lack of Sigstore provenance is consistent across all versions and not a security risk for this package. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 0.10.5 | 5 / 13 | |
| 0.10.4 | 4 / 14 | |
| 0.10.3 | 4 / 17 | |
| 0.10.1 | 4 / 17 | |
| 0.10.0 | 4 / 17 | |
| 0.9.24 | 4 / 12 | |
| 0.9.23 | 4 / 12 | |
| 0.9.22 | 4 / 12 | |
| 0.9.21 | 4 / 12 | |
| 0.9.20 | 4 / 12 | |
| 0.9.19 | 4 / 12 | |
| 0.9.18 | 4 / 11 | |
| 0.9.17 | 4 / 11 | |
| 0.9.16 | 4 / 11 | |
| 0.9.15 | 4 / 11 | |
| 0.9.14 | 4 / 11 | |
| 0.9.13 | 4 / 11 | |
| 0.9.12 | 4 / 11 | |
| 0.9.11 | 4 / 11 | |
| 0.9.10 | 4 / 9 | |
| 0.9.9 | 4 / 7 | |
| 0.9.8 | 4 / 7 | |
| 0.9.7 | 4 / 7 | |
| 0.9.6 | 4 / 7 | |
| 0.9.5 | 4 / 7 | |
| 0.9.4 | 4 / 7 | |
| 0.9.3 | 4 / 7 | |
| 0.9.2 | 4 / 7 | |
| 0.9.1 | 4 / 7 | |
| 0.9.0 | 4 / 7 | |
| 0.8.15 | 4 / 6 | |
| 0.8.14 | 5 / 6 | |
| 0.8.13 | 5 / 6 | |
| 0.8.12 | 5 / 6 | |
| 0.8.11 | 5 / 6 | |
| 0.8.10 | 5 / 6 | |
| 0.8.9 | 5 / 6 | |
| 0.8.8 | 5 / 6 | |
| 0.8.7 | 5 / 6 | |
| 0.8.6 | 5 / 6 | |
| 0.8.5 | 5 / 6 | |
| 0.8.4 | 5 / 6 | |
| 0.8.3 | 5 / 6 | |
| 0.8.2 | 5 / 6 | |
| 0.8.1 | 5 / 6 | |
| 0.8.0 | 5 / 6 | |
| 0.7.15 | 5 / 5 | |
| 0.7.14 | 5 / 5 | |
| 0.7.13 | 5 / 5 | |
| 0.7.12 | 5 / 5 | |
| 0.7.11 | 5 / 5 |
v0.10.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: uifrnbot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.