@fluentui-react-native/experimental-shimmer
A cross-platform Fluent Shimmer 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): Microsoft-owned monorepo package published by trusted bot; build tooling migration explains the missing gitHead. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @fluentui-react-native scoped package; consistent with org's internal refactoring pattern. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package within the same Microsoft fluentui-react-native monorepo; always a legitimate internal dependency for this package. | ai |
Versions (showing 51 of 200)
| Version | Deps | Published |
|---|---|---|
| 0.14.5 | 6 / 15 | |
| 0.14.4 | 5 / 16 | |
| 0.14.3 | 5 / 20 | |
| 0.14.1 | 5 / 20 | |
| 0.14.0 | 5 / 20 | |
| 0.13.20 | 5 / 15 | |
| 0.13.19 | 5 / 15 | |
| 0.13.18 | 5 / 15 | |
| 0.13.17 | 5 / 15 | |
| 0.13.16 | 5 / 15 | |
| 0.13.15 | 5 / 15 | |
| 0.13.14 | 5 / 11 | |
| 0.13.13 | 5 / 11 | |
| 0.13.12 | 5 / 11 | |
| 0.13.11 | 5 / 11 | |
| 0.13.10 | 5 / 11 | |
| 0.13.9 | 5 / 11 | |
| 0.13.8 | 5 / 11 | |
| 0.13.7 | 5 / 11 | |
| 0.13.6 | 5 / 9 | |
| 0.13.5 | 5 / 7 | |
| 0.13.4 | 5 / 7 | |
| 0.13.3 | 5 / 7 | |
| 0.13.2 | 5 / 7 | |
| 0.13.1 | 5 / 7 | |
| 0.13.0 | 5 / 7 | |
| 0.12.15 | 5 / 6 | |
| 0.12.14 | 6 / 6 | |
| 0.12.13 | 6 / 6 | |
| 0.12.12 | 6 / 6 | |
| 0.12.11 | 5 / 7 | |
| 0.12.10 | 5 / 7 | |
| 0.12.9 | 5 / 7 | |
| 0.12.8 | 5 / 7 | |
| 0.12.7 | 5 / 7 | |
| 0.12.6 | 5 / 7 | |
| 0.12.5 | 5 / 7 | |
| 0.12.4 | 5 / 7 | |
| 0.12.3 | 5 / 7 | |
| 0.12.2 | 5 / 7 | |
| 0.12.1 | 5 / 7 | |
| 0.12.0 | 5 / 7 | |
| 0.11.6 | 5 / 6 | |
| 0.11.5 | 5 / 6 | |
| 0.11.4 | 5 / 6 | |
| 0.11.3 | 5 / 6 | |
| 0.11.2 | 5 / 6 | |
| 0.11.1 | 5 / 6 | |
| 0.11.0 | 5 / 6 | |
| 0.10.8 | 5 / 6 | |
| 0.10.7 | 5 / 6 |
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.