simplebar-core
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): gromy is a long-standing npm account (1879 days, 144 approved packages) and repo/homepage URLs remain unchanged pointing to original grsmto/simplebar. Consistent with legitimate account transition. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to gromy occurred in 2021; gromy has a strong track record and no code/script changes were introduced. Legitimate maintainer transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): gromy is a trusted long-standing npm account; addition is consistent with legitimate handoff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of grsmto is consistent with the documented maintainer transition; no malicious indicators present. | ai | |
| source-diff | net-exec-file:dist/simplebar-core.js | AI (source-diff): dist/simplebar-core.js is a standard rollup UMD bundle. The 'network+exec' signals are lodash's global detection idiom (Function('return this')()) and URL comments — not malicious. Stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): simplebar-core is a legitimate monorepo sub-package; README links to main package docs (expected for monorepo structure). No keywords is a minor style issue, not a spam indicator. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 2 / 2 | |
| 1.3.1 | 2 / 2 | |
| 1.3.0 | 1 / 1 | |
| 1.2.6 | 3 / 1 | |
| 1.2.5 | 4 / 1 | |
| 1.2.4 | 4 / 1 | |
| 1.2.3 | 4 / 1 | |
| 1.2.2 | 3 / 2 | |
| 1.2.1 | 2 / 3 | |
| 1.2.0 | 2 / 2 | |
| 1.1.1 | 2 / 2 | |
| 1.1.0 | 2 / 2 | |
| 1.0.10 | 2 / 2 | |
| 1.0.9 | 2 / 2 | |
| 1.0.8 | 2 / 4 | |
| 1.0.7 | 3 / 5 | |
| 1.0.6 | 3 / 5 | |
| 1.0.5 | 3 / 5 | |
| 1.0.4 | 2 / 5 | |
| 1.0.3 | 2 / 5 | |
| 1.0.2 | 2 / 5 | |
| 1.0.1 | 2 / 5 | |
| 1.0.0 | 4 / 12 |
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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
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.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
3 findingsAll previous maintainers (grsmto) were replaced by new maintainers (gromy). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2021-03-01. 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.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.