@griffel/core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @griffel/core is a scoped Microsoft package (github.com/microsoft/griffel). 'core' is a standard sub-package name; no impersonation of 'cors' is plausible. False positive for this package. | ai | |
| dependencies | unvetted-dep:@griffel/style-types | AI (dependencies): @griffel/style-types is a sibling package in the same Microsoft Griffel monorepo; dependency is expected and legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Microsoft package with 55 versions and 4+ year history. Short README and no keywords are cosmetic issues, not spam indicators. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.21.2 | 6 / 0 | |
| 1.21.1 | 6 / 0 | |
| 1.21.0 | 6 / 0 | |
| 1.20.3 | 6 / 0 | |
| 1.20.2 | 6 / 0 | |
| 1.20.1 | 6 / 0 | |
| 1.20.0 | 6 / 0 |
v1.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
2 findingsPackage name '@griffel/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.