← Home

@fluentui-react-native/vibrancy-view

npm Repository Homepage

A native wrapper for NSVisualEffectView on macOS

22
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jasonvmorseacoatesuifrnbothansenyy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Microsoft monorepo bot publisher with strong track record; dormancy reflects upstream release cadence, not takeover risk. ai
provenance missing-githead AI (provenance): Build tooling change (tsgo) plausibly explains missing gitHead; publisher track record is clean. ai

Versions (showing 22 of 22)

Version Deps Published
0.4.5 1 / 12
0.4.4 1 / 12
0.4.3 1 / 15
0.4.1 1 / 15
0.4.0 1 / 15
0.3.5 1 / 11
0.3.4 2 / 10
0.3.3 2 / 10
0.3.2 2 / 10
0.3.1 2 / 8
0.3.0 2 / 6
0.2.2 2 / 6
0.2.1 2 / 6
0.2.0 2 / 6
0.1.5 2 / 5
0.1.4 3 / 5
0.1.3 3 / 5
0.1.2 3 / 5
0.1.1 3 / 5
0.1.0 3 / 5
0.0.3 3 / 4
0.0.2 3 / 4

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.