@uifabricshared/theming-ramp
Theming Library
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a Microsoft org-level maintainer account; addition is consistent with Microsoft's OSS release automation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects the package being deprecated/stable; resumed publish is bot-driven under the official Microsoft fluentui-react-native org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Microsoft FluentUI sub-package; sparse README/keywords are typical for internal monorepo packages. | ai |
Versions (showing 51 of 209)
| Version | Deps | Published |
|---|---|---|
| 0.21.4 | 3 / 7 | |
| 0.21.3 | 3 / 10 | |
| 0.21.1 | 3 / 10 | |
| 0.21.0 | 3 / 10 | |
| 0.20.17 | 3 / 10 | |
| 0.20.16 | 3 / 10 | |
| 0.20.15 | 3 / 10 | |
| 0.20.14 | 3 / 10 | |
| 0.20.13 | 3 / 10 | |
| 0.20.12 | 3 / 10 | |
| 0.20.11 | 3 / 8 | |
| 0.20.10 | 3 / 8 | |
| 0.20.9 | 3 / 8 | |
| 0.20.8 | 3 / 8 | |
| 0.20.7 | 3 / 8 | |
| 0.20.6 | 3 / 8 | |
| 0.20.5 | 3 / 8 | |
| 0.20.4 | 3 / 8 | |
| 0.20.3 | 3 / 8 | |
| 0.20.2 | 3 / 6 | |
| 0.20.1 | 3 / 6 | |
| 0.20.0 | 3 / 6 | |
| 0.19.12 | 3 / 6 | |
| 0.19.11 | 3 / 6 | |
| 0.19.10 | 3 / 6 | |
| 0.19.9 | 3 / 6 | |
| 0.19.8 | 3 / 6 | |
| 0.19.7 | 3 / 6 | |
| 0.19.6 | 3 / 6 | |
| 0.19.5 | 3 / 6 | |
| 0.19.4 | 3 / 6 | |
| 0.19.3 | 3 / 6 | |
| 0.19.2 | 3 / 6 | |
| 0.19.1 | 3 / 6 | |
| 0.19.0 | 3 / 6 | |
| 0.18.0 | 3 / 6 | |
| 0.17.24 | 3 / 6 | |
| 0.17.23 | 3 / 6 | |
| 0.17.22 | 3 / 6 | |
| 0.17.21 | 3 / 6 | |
| 0.17.20 | 3 / 6 | |
| 0.17.19 | 3 / 6 | |
| 0.17.18 | 3 / 6 | |
| 0.17.17 | 3 / 6 | |
| 0.17.16 | 3 / 6 | |
| 0.17.15 | 3 / 6 | |
| 0.17.14 | 3 / 6 | |
| 0.17.13 | 3 / 6 | |
| 0.17.12 | 3 / 6 | |
| 0.17.11 | 3 / 6 | |
| 0.17.10 | 3 / 6 |
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.