simplebar
Scrollbars, simpler.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): grsmto→gromy is the same maintainer (Adrien Denat) renaming their npm account; gromy has 146 approved packages and 1879 days of history. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): gromy is the same person as grsmto (account rename); long-standing trusted publisher. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): grsmto removed because the account was renamed to gromy; not a takeover. | ai | |
| provenance | missing-githead | AI (provenance): Monorepo publish flow commonly drops gitHead; same trusted maintainer (gromy) with long history. Stable for this package. | ai |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 6.3.3 | 1 / 4 | |
| 6.3.2 | 1 / 4 | |
| 6.3.1 | 1 / 4 | |
| 6.3.0 | 1 / 4 | |
| 6.2.7 | 2 / 4 | |
| 6.2.6 | 2 / 4 | |
| 6.2.5 | 2 / 4 | |
| 6.2.4 | 2 / 4 | |
| 6.2.3 | 2 / 4 | |
| 6.2.2 | 2 / 4 | |
| 6.2.1 | 2 / 4 | |
| 6.2.0 | 2 / 4 | |
| 6.1.1 | 2 / 4 | |
| 6.1.0 | 2 / 4 | |
| 6.0.0 | 2 / 4 | |
| 5.3.9 | 6 / 7 | |
| 5.3.8 | 6 / 7 | |
| 5.3.7 | 6 / 7 | |
| 5.3.6 | 6 / 7 | |
| 5.3.5 | 6 / 7 | |
| 5.3.4 | 6 / 7 | |
| 5.3.3 | 6 / 7 | |
| 5.3.2 | 6 / 7 | |
| 5.3.0 | 6 / 7 | |
| 5.2.1 | 6 / 7 | |
| 5.2.0 | 6 / 7 | |
| 5.1.0 | 6 / 7 | |
| 5.0.7 | 6 / 7 | |
| 5.0.6 | 6 / 7 | |
| 5.0.5 | 6 / 7 | |
| 5.0.4 | 6 / 7 | |
| 5.0.3 | 6 / 7 | |
| 5.0.2 | 6 / 7 | |
| 5.0.1 | 6 / 7 | |
| 5.0.0 | 6 / 7 | |
| 4.2.3 | 6 / 5 | |
| 4.2.2 | 6 / 5 | |
| 4.2.1 | 6 / 5 | |
| 4.2.0 | 6 / 5 | |
| 4.1.0 | 6 / 5 | |
| 4.0.0 | 7 / 5 | |
| 3.1.5 | 7 / 5 | |
| 3.1.4 | 7 / 5 | |
| 3.1.3 | 7 / 5 | |
| 3.1.2 | 7 / 5 | |
| 3.1.1 | 6 / 5 | |
| 3.1.0 | 6 / 5 | |
| 2.6.1 | 4 / 18 | |
| 2.6.0 | 4 / 18 | |
| 2.5.1 | 4 / 14 | |
| 2.5.0 | 3 / 14 |
v6.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gromy.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
2 findingsThis version was published by a different npm account than previous versions on 2021-05-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
2 findingsThis version was published by a different npm account than previous versions on 2021-04-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.