@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, 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): Trusted Microsoft org bot publisher; build toolchain change explains missing gitHead without indicating supply-chain compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party @fluentui-react-native package from the same Microsoft monorepo; not a supply-chain risk. | ai | |
| 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 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.5.5 | 5 / 14 | |
| 0.5.4 | 4 / 15 | |
| 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 | |
| 0.4.4 | 4 / 6 | |
| 0.4.3 | 4 / 6 | |
| 0.4.2 | 4 / 6 | |
| 0.4.1 | 4 / 6 | |
| 0.4.0 | 4 / 6 | |
| 0.3.13 | 4 / 5 | |
| 0.3.12 | 4 / 5 | |
| 0.3.11 | 4 / 5 | |
| 0.3.10 | 4 / 5 | |
| 0.3.9 | 4 / 5 | |
| 0.3.8 | 4 / 5 | |
| 0.3.7 | 4 / 5 | |
| 0.3.6 | 4 / 5 | |
| 0.3.5 | 4 / 5 | |
| 0.3.4 | 4 / 5 | |
| 0.3.3 | 4 / 5 | |
| 0.3.2 | 4 / 5 | |
| 0.3.1 | 4 / 5 | |
| 0.3.0 | 4 / 5 | |
| 0.2.13 | 4 / 4 | |
| 0.2.12 | 4 / 4 | |
| 0.2.11 | 4 / 4 | |
| 0.2.10 | 4 / 4 | |
| 0.2.9 | 4 / 4 | |
| 0.2.8 | 4 / 4 | |
| 0.2.7 | 4 / 4 | |
| 0.2.6 | 4 / 4 | |
| 0.2.5 | 4 / 4 | |
| 0.2.4 | 4 / 4 | |
| 0.2.3 | 4 / 4 | |
| 0.2.2 | 4 / 4 | |
| 0.2.1 | 4 / 4 | |
| 0.2.0 | 4 / 4 | |
| 0.1.1 | 4 / 4 | |
| 0.1.0 | 4 / 4 |
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.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.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.1.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.