@fluentui-react-native/drawer
A cross-platform Drawer component using the Fluent Design System
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package within the same Microsoft FluentUI React Native monorepo; unvetted status is a registry artifact, not a security concern. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/theme-tokens | AI (dependencies): Sibling package within the same Microsoft FluentUI React Native monorepo; unvetted status is a registry artifact, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft monorepo package published via automation bot; lack of Sigstore provenance is consistent across all versions and not a security risk here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.5.3 | 4 / 19 | |
| 0.5.1 | 4 / 19 | |
| 0.5.0 | 4 / 19 | |
| 0.4.19 | 4 / 14 | |
| 0.4.18 | 4 / 14 | |
| 0.4.17 | 4 / 14 | |
| 0.4.16 | 4 / 14 | |
| 0.4.15 | 4 / 14 | |
| 0.4.14 | 4 / 14 | |
| 0.4.13 | 4 / 10 | |
| 0.4.12 | 4 / 10 | |
| 0.4.11 | 4 / 10 | |
| 0.4.10 | 4 / 10 | |
| 0.4.9 | 4 / 10 | |
| 0.4.8 | 4 / 10 | |
| 0.4.7 | 4 / 10 | |
| 0.4.6 | 4 / 10 | |
| 0.4.5 | 4 / 7 |
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
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.5.0
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.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.