@fluentui-react-native/use-slot
Hook function to use a component as a pluggable slot
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): Part of a large Microsoft monorepo; inactivity reflects upstream release cadence, not abandonment or takeover. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/merge-props | AI (dependencies): Same-org monorepo sibling dependency; stable false positive for this package family. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 1 / 13 | |
| 0.7.3 | 1 / 17 | |
| 0.7.1 | 1 / 17 | |
| 0.7.0 | 1 / 17 | |
| 0.6.12 | 1 / 11 | |
| 0.6.11 | 2 / 6 | |
| 0.6.10 | 2 / 6 | |
| 0.6.9 | 2 / 6 | |
| 0.6.8 | 2 / 6 | |
| 0.6.7 | 2 / 6 | |
| 0.6.6 | 2 / 6 | |
| 0.6.5 | 2 / 6 | |
| 0.6.4 | 2 / 6 | |
| 0.6.3 | 2 / 6 | |
| 0.6.2 | 2 / 5 | |
| 0.6.1 | 2 / 5 | |
| 0.6.0 | 2 / 5 | |
| 0.5.2 | 2 / 4 | |
| 0.5.1 | 2 / 4 | |
| 0.5.0 | 2 / 4 | |
| 0.4.2 | 2 / 3 | |
| 0.4.1 | 2 / 3 | |
| 0.4.0 | 2 / 3 | |
| 0.3.4 | 2 / 3 | |
| 0.3.3 | 2 / 3 | |
| 0.3.2 | 2 / 3 | |
| 0.3.1 | 2 / 3 | |
| 0.3.0 | 2 / 3 | |
| 0.2.6 | 2 / 3 | |
| 0.2.5 | 2 / 3 | |
| 0.2.4 | 2 / 3 | |
| 0.2.3 | 2 / 3 | |
| 0.2.2 | 2 / 3 | |
| 0.2.1 | 2 / 3 | |
| 0.2.0 | 2 / 3 | |
| 0.1.7 | 2 / 3 | |
| 0.1.6 | 1 / 3 | |
| 0.1.5 | 1 / 3 | |
| 0.1.4 | 1 / 3 | |
| 0.1.3 | 1 / 3 | |
| 0.1.2 | 1 / 3 |
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
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.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.