@fluentui/react-jsx-runtime
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 | no-provenance | AI (provenance): Established Microsoft FluentUI monorepo package; lack of Sigstore provenance is not a meaningful risk signal for this well-known publisher. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): @fluentui/react-utilities is a first-party Microsoft FluentUI package from the same monorepo; dependency is expected and legitimate. | ai |
Versions (showing 51 of 77)
| Version | Deps | Published |
|---|---|---|
| 9.4.4 | 2 / 0 | |
| 9.4.3 | 2 / 0 | |
| 9.4.2 | 2 / 0 | |
| 9.4.1 | 2 / 0 | |
| 9.4.0 | 2 / 0 | |
| 9.3.5 | 3 / 0 | |
| 9.3.4 | 3 / 4 | |
| 9.3.3 | 3 / 4 | |
| 9.3.2 | 3 / 4 | |
| 9.3.1 | 3 / 4 | |
| 9.3.0 | 3 / 4 | |
| 9.2.2 | 3 / 4 | |
| 9.2.1 | 3 / 4 | |
| 9.2.0 | 3 / 4 | |
| 9.1.6 | 3 / 4 | |
| 9.1.5 | 3 / 4 | |
| 9.1.4 | 3 / 4 | |
| 9.1.3 | 3 / 4 | |
| 9.1.2 | 3 / 4 | |
| 9.1.1 | 3 / 4 | |
| 9.1.0 | 3 / 4 | |
| 9.0.55 | 3 / 4 | |
| 9.0.54 | 3 / 4 | |
| 9.0.53 | 3 / 4 | |
| 9.0.52 | 3 / 4 | |
| 9.0.51 | 3 / 4 | |
| 9.0.50 | 3 / 4 | |
| 9.0.49 | 3 / 4 | |
| 9.0.48 | 3 / 4 | |
| 9.0.47 | 3 / 4 | |
| 9.0.46 | 3 / 4 | |
| 9.0.45 | 3 / 5 | |
| 9.0.44 | 3 / 5 | |
| 9.0.43 | 3 / 5 | |
| 9.0.42 | 3 / 5 | |
| 9.0.41 | 3 / 5 | |
| 9.0.40 | 3 / 5 | |
| 9.0.39 | 3 / 5 | |
| 9.0.38 | 3 / 5 | |
| 9.0.37 | 3 / 5 | |
| 9.0.36 | 3 / 5 | |
| 9.0.35 | 3 / 5 | |
| 9.0.34 | 3 / 5 | |
| 9.0.33 | 3 / 5 | |
| 9.0.32 | 3 / 5 | |
| 9.0.31 | 3 / 5 | |
| 9.0.30 | 3 / 5 | |
| 9.0.29 | 3 / 5 | |
| 9.0.28 | 3 / 5 | |
| 9.0.27 | 3 / 5 | |
| 9.0.26 | 3 / 5 |
v9.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.