react-perfect-scrollbar
A react wrapper for perfect-scrollbar
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/react-perfect-scrollbar.js | AI (source-diff): This is a standard Webpack UMD bundle (webpackUniversalModuleDefinition pattern), not obfuscation. The build pipeline addition in this version explains its presence; stable for this package. | ai | |
| source-diff | obfuscated-file:lib/react-perfect-scrollbar.js | AI (source-diff): File is standard Webpack bundle output (webpackBootstrap pattern clearly visible in sample). This package ships pre-built webpack artifacts; minified bundle files are expected and stable for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is explained by the addition of webpack-compiled lib/ artifacts (bundle + source maps). Expected for a library that began shipping pre-built output. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 1.5.8 | 2 / 28 | |
| 1.5.7 | 2 / 28 | |
| 1.5.6 | 2 / 28 | |
| 1.5.5 | 2 / 28 | |
| 1.5.4 | 2 / 28 | |
| 1.5.3 | 2 / 28 | |
| 1.5.2 | 2 / 28 | |
| 1.5.1 | 2 / 28 | |
| 1.5.0 | 2 / 28 | |
| 1.4.4 | 2 / 28 | |
| 1.4.2 | 2 / 28 | |
| 1.4.1 | 2 / 28 | |
| 1.4.0 | 2 / 27 | |
| 1.2.2 | 2 / 27 | |
| 1.2.1 | 2 / 27 | |
| 1.2.0 | 4 / 25 | |
| 1.1.3 | 4 / 25 | |
| 1.1.2 | 4 / 25 | |
| 1.1.1 | 4 / 25 | |
| 1.1.0 | 4 / 25 | |
| 1.0.5 | 4 / 25 | |
| 1.0.4 | 4 / 25 | |
| 1.0.3 | 4 / 25 | |
| 1.0.2 | 4 / 25 | |
| 1.0.1 | 4 / 25 | |
| 1.0.0 | 4 / 25 | |
| 0.2.5 | 4 / 25 | |
| 0.2.4 | 4 / 25 | |
| 0.2.3 | 4 / 25 | |
| 0.2.2 | 4 / 25 | |
| 0.2.1 | 2 / 25 | |
| 0.2.0 | 1 / 25 | |
| 0.1.5 | 1 / 24 | |
| 0.1.4 | 1 / 24 | |
| 0.1.2 | 1 / 23 | |
| 0.1.1 | 1 / 22 | |
| 0.1.0 | 1 / 22 |
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.4
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.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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
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.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.