react-lib-tools
Tools for creating documentation for React component libraries. Used by packages like `react-window`, `react-resizable-panels`, and others.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/VersionsRoute-Br6RZivR.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; not obfuscated, readable React component code. | ai | |
| source-diff | obfuscated-file:dist/index-DleNtYr0.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; not obfuscated, readable React component code. | ai | |
| source-diff | obfuscated-file:dist/index-Dv2f5CFF.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; sample shows readable React component code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/VersionsRoute-3iGt23Bt.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; sample shows readable React/SVG component code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/VersionsRoute-WwJGbKHn.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; content is readable React components. | ai | |
| source-diff | obfuscated-file:dist/index-Dishg8MY.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; content is readable React/SVG components. | ai | |
| source-diff | obfuscated-file:dist/index-BWhTJgvX.cjs | AI (source-diff): Standard minified React component bundle; content is clearly recognizable UI code. | ai | |
| source-diff | obfuscated-file:dist/index-CplpUoHk.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; not obfuscated, code is readable React components. | ai | |
| source-diff | obfuscated-file:dist/VersionsRoute-DhLe3vGU.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; not obfuscated, code is readable React components. | ai | |
| source-diff | obfuscated-file:dist/index-rOOr2GGh.cjs | AI (source-diff): Standard minified CJS bundle of React component library; readable SVG/React code, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/fuse-CM2wbN_z.cjs | AI (source-diff): Standard minified CJS bundle of fuse.js; readable code, no malicious patterns. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are @codemirror/* and @lezer/* — well-established CodeMirror 6 ecosystem packages consistent with adding editor functionality. | ai | |
| source-diff | obfuscated-file:dist/index-8LP1ujuh.cjs | AI (source-diff): Standard Vite/Rollup minified bundle; sample shows readable React component code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/VersionsRoute-DTaE8zr5.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; readable React component code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-BFh5cQOB.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; readable React component code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-MEfvl32g.cjs | AI (source-diff): Standard Vite minified bundle output; code is readable React/SVG components, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/VersionsRoute-D5nKJAiH.cjs | AI (source-diff): Standard Vite minified bundle output; code is readable React components, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-BCwWYpnQ.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; sample shows readable React component code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/VersionsRoute-CX3YF7an.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; sample shows readable React component code, not malicious obfuscation. | ai | |
| phantom-deps | phantom-dep:@codemirror/lang-markdown | AI (phantom-deps): Config-file reference only; not a real import gap for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.0.53 | 10 / 60 | |
| 0.0.51 | 10 / 60 | |
| 0.0.50 | 10 / 60 | |
| 0.0.43 | 11 / 60 | |
| 0.0.42 | 11 / 60 | |
| 0.0.39 | 11 / 61 | |
| 0.0.34 | 9 / 61 | |
| 0.0.33 | 9 / 61 | |
| 0.0.32 | 9 / 61 | |
| 0.0.31 | 9 / 61 | |
| 0.0.30 | 9 / 61 | |
| 0.0.28 | 8 / 61 | |
| 0.0.24 | 8 / 61 | |
| 0.0.23 | 8 / 61 | |
| 0.0.21 | 8 / 56 | |
| 0.0.19 | 8 / 56 | |
| 0.0.16 | 0 / 64 | |
| 0.0.14 | 0 / 64 | |
| 0.0.13 | 0 / 64 | |
| 0.0.12 | 0 / 64 | |
| 0.0.11 | 0 / 64 | |
| 0.0.10 | 0 / 64 | |
| 0.0.9 | 0 / 64 | |
| 0.0.8 | 0 / 64 | |
| 0.0.7 | 0 / 64 | |
| 0.0.6 | 0 / 64 | |
| 0.0.5 | 0 / 64 | |
| 0.0.4 | 0 / 64 | |
| 0.0.3 | 0 / 64 | |
| 0.0.2 | 0 / 64 | |
| 0.0.1 | 0 / 64 |
v0.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.43
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.42
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.39
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.34
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.0.33
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.0.32
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.0.31
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.0.30
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.28
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.24
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.23
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.21
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.19
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.16
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.