@fluentui/react-context-selector
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): Microsoft FluentUI packages do not currently publish Sigstore provenance; this is consistent across the entire package family and not a risk indicator. | ai |
Versions (showing 51 of 103)
| Version | Deps | Published |
|---|---|---|
| 9.2.18 | 2 / 1 | |
| 9.2.17 | 2 / 1 | |
| 9.2.16 | 2 / 0 | |
| 9.2.15 | 2 / 0 | |
| 9.2.14 | 2 / 0 | |
| 9.2.13 | 2 / 2 | |
| 9.2.12 | 2 / 2 | |
| 9.2.11 | 2 / 2 | |
| 9.2.10 | 2 / 2 | |
| 9.2.9 | 2 / 2 | |
| 9.2.8 | 2 / 2 | |
| 9.2.7 | 2 / 2 | |
| 9.2.6 | 2 / 2 | |
| 9.2.5 | 2 / 2 | |
| 9.2.4 | 2 / 2 | |
| 9.2.3 | 2 / 2 | |
| 9.2.2 | 2 / 2 | |
| 9.2.1 | 2 / 2 | |
| 9.2.0 | 2 / 2 | |
| 9.1.77 | 2 / 2 | |
| 9.1.76 | 2 / 2 | |
| 9.1.75 | 2 / 2 | |
| 9.1.74 | 2 / 2 | |
| 9.1.73 | 2 / 2 | |
| 9.1.72 | 2 / 2 | |
| 9.1.71 | 2 / 2 | |
| 9.1.70 | 2 / 2 | |
| 9.1.69 | 2 / 2 | |
| 9.1.68 | 2 / 3 | |
| 9.1.67 | 2 / 3 | |
| 9.1.66 | 2 / 3 | |
| 9.1.65 | 2 / 3 | |
| 9.1.64 | 2 / 3 | |
| 9.1.63 | 2 / 3 | |
| 9.1.62 | 2 / 3 | |
| 9.1.61 | 2 / 3 | |
| 9.1.60 | 2 / 3 | |
| 9.1.59 | 2 / 3 | |
| 9.1.58 | 2 / 3 | |
| 9.1.57 | 2 / 3 | |
| 9.1.56 | 2 / 3 | |
| 9.1.55 | 2 / 3 | |
| 9.1.54 | 2 / 3 | |
| 9.1.53 | 2 / 3 | |
| 9.1.52 | 2 / 3 | |
| 9.1.51 | 2 / 3 | |
| 9.1.50 | 2 / 3 | |
| 9.1.49 | 2 / 3 | |
| 9.1.48 | 2 / 3 | |
| 9.1.47 | 2 / 3 | |
| 9.1.46 | 2 / 3 |
v9.1.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.60
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.1.59
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.1.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.