@griffel/react
React implementation of Atomic CSS-in-JS
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a legitimate declared runtime dependency for compiled TypeScript output in this Microsoft package; not a true phantom dependency. | ai | |
| dependencies | unvetted-dep:@griffel/core | AI (dependencies): @griffel/core is the sibling first-party package from the same Microsoft/Griffel monorepo; stable and expected dependency for this package. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 1.7.6 | 2 / 1 | |
| 1.7.5 | 2 / 1 | |
| 1.7.4 | 2 / 0 | |
| 1.7.3 | 2 / 0 | |
| 1.7.2 | 2 / 0 | |
| 1.7.1 | 2 / 0 | |
| 1.7.0 | 2 / 0 | |
| 1.6.2 | 2 / 0 | |
| 1.6.1 | 2 / 0 | |
| 1.6.0 | 2 / 0 | |
| 1.5.32 | 2 / 0 | |
| 1.5.31 | 2 / 0 | |
| 1.5.30 | 2 / 0 | |
| 1.5.29 | 2 / 0 | |
| 1.5.28 | 2 / 0 | |
| 1.5.27 | 2 / 0 | |
| 1.5.26 | 2 / 0 | |
| 1.5.25 | 2 / 0 | |
| 1.5.24 | 2 / 0 | |
| 1.5.23 | 2 / 0 | |
| 1.5.22 | 2 / 0 | |
| 1.5.21 | 2 / 0 | |
| 1.5.20 | 2 / 0 | |
| 1.5.19 | 2 / 0 | |
| 1.5.18 | 2 / 0 | |
| 1.5.17 | 2 / 0 | |
| 1.5.16 | 2 / 0 | |
| 1.5.15 | 2 / 0 | |
| 1.5.14 | 2 / 0 | |
| 1.5.13 | 2 / 0 | |
| 1.5.12 | 2 / 0 | |
| 1.5.11 | 2 / 0 | |
| 1.5.10 | 2 / 0 | |
| 1.5.9 | 2 / 0 | |
| 1.5.8 | 2 / 0 | |
| 1.5.7 | 2 / 0 | |
| 1.5.6 | 2 / 0 | |
| 1.5.5 | 2 / 0 | |
| 1.5.4 | 2 / 0 | |
| 1.5.3 | 2 / 0 | |
| 1.5.2 | 2 / 0 | |
| 1.5.1 | 2 / 0 | |
| 1.5.0 | 2 / 0 | |
| 1.4.3 | 2 / 0 | |
| 1.4.2 | 2 / 0 | |
| 1.4.1 | 2 / 0 | |
| 1.4.0 | 2 / 0 | |
| 1.3.2 | 2 / 0 | |
| 1.3.1 | 2 / 0 | |
| 1.3.0 | 2 / 0 | |
| 1.2.3 | 2 / 0 |
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.