@fluentui-react-native/adapters
Adapters for working with react-native types
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Active Microsoft monorepo with 131 versions; publish gap is not indicative of account takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Utility sub-package of a large Microsoft OSS monorepo; sparse README and no keywords are expected for internal utility packages. | ai |
Versions (showing 30 of 130)
| Version | Deps | Published |
|---|---|---|
| 0.2.23 | 0 / 8 | |
| 0.2.22 | 0 / 8 | |
| 0.2.21 | 0 / 8 | |
| 0.2.20 | 0 / 8 | |
| 0.2.19 | 0 / 8 | |
| 0.2.18 | 0 / 8 | |
| 0.2.17 | 0 / 8 | |
| 0.2.16 | 0 / 8 | |
| 0.2.15 | 0 / 8 | |
| 0.2.14 | 0 / 8 | |
| 0.2.13 | 0 / 8 | |
| 0.2.12 | 0 / 8 | |
| 0.2.11 | 0 / 8 | |
| 0.2.10 | 0 / 8 | |
| 0.2.9 | 0 / 8 | |
| 0.2.8 | 0 / 8 | |
| 0.2.7 | 0 / 8 | |
| 0.2.6 | 0 / 8 | |
| 0.2.5 | 0 / 8 | |
| 0.2.4 | 0 / 8 | |
| 0.2.3 | 0 / 8 | |
| 0.2.2 | 0 / 8 | |
| 0.2.0 | 0 / 8 | |
| 0.1.7 | 0 / 8 | |
| 0.1.6 | 0 / 8 | |
| 0.1.5 | 0 / 8 | |
| 0.1.4 | 0 / 8 | |
| 0.1.3 | 0 / 7 | |
| 0.1.2 | 0 / 7 | |
| 0.1.1 | 0 / 7 |
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.