@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, 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 | publisher-changed-stale | AI (provenance): Long-stable publisher change from 2022, not a takeover pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same long-standing maintainer transition, consistent history since. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency. | ai | |
| 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 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 1.21.3 | 6 / 0 | |
| 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 | |
| 1.19.2 | 6 / 0 | |
| 1.19.1 | 6 / 0 | |
| 1.19.0 | 6 / 0 | |
| 1.18.2 | 6 / 0 | |
| 1.18.1 | 6 / 0 | |
| 1.18.0 | 6 / 0 | |
| 1.17.1 | 6 / 0 | |
| 1.17.0 | 6 / 0 | |
| 1.16.0 | 6 / 0 | |
| 1.15.3 | 6 / 0 | |
| 1.15.2 | 6 / 0 | |
| 1.15.1 | 6 / 0 | |
| 1.15.0 | 6 / 0 | |
| 1.14.4 | 6 / 0 | |
| 1.14.3 | 6 / 0 | |
| 1.14.2 | 6 / 0 | |
| 1.14.1 | 6 / 0 | |
| 1.14.0 | 6 / 0 | |
| 1.13.1 | 6 / 0 | |
| 1.13.0 | 5 / 0 | |
| 1.12.2 | 5 / 0 | |
| 1.12.1 | 5 / 0 | |
| 1.12.0 | 5 / 0 | |
| 1.11.0 | 5 / 0 | |
| 1.10.1 | 5 / 0 | |
| 1.10.0 | 5 / 0 | |
| 1.9.2 | 5 / 0 | |
| 1.9.1 | 5 / 0 | |
| 1.9.0 | 5 / 0 | |
| 1.8.3 | 5 / 0 | |
| 1.8.2 | 5 / 0 | |
| 1.8.1 | 5 / 0 | |
| 1.8.0 | 5 / 0 | |
| 1.7.0 | 5 / 0 | |
| 1.6.1 | 5 / 0 | |
| 1.6.0 | 5 / 0 | |
| 1.5.1 | 5 / 0 | |
| 1.5.0 | 5 / 0 | |
| 1.4.1 | 5 / 0 | |
| 1.4.0 | 5 / 0 | |
| 1.3.1 | 5 / 0 | |
| 1.3.0 | 5 / 0 | |
| 1.2.0 | 5 / 0 |
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
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.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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version was published by a different npm account (uifabricteam) than the most recent previously approved version (layershifter) on 2022-05-04. It has since remained available on npm for 1538 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account (uifabricteam) than the most recent previously approved version (layershifter) on 2022-04-06. It has since remained available on npm for 1566 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.