@react-form-builder/components-rsuite
OptimaJet Form Builder Components - RSuite
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/formengine-rsuite.css-DkGUHOws.js | AI (source-diff): Base64-encoded CSS data URI — standard Vite inline-css build artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/rSuiteComponentsDescriptions-CaJ33mxP.js | AI (source-diff): File is a minified component-descriptions bundle with readable prop/component metadata; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/rsuite-no-reset.min.css-bW1P11UK.js | AI (source-diff): CSS inlined as base64 data URI via Vite build; decodes to plain RSuite theme CSS, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/rSuiteComponentsDescriptions-lX1mwx9_.js | AI (source-diff): Plaintext JS object with component prop descriptions; long lines from minified JSON, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/formengine-rsuite.css-B1zD3_ue.js | AI (source-diff): CSS inlined as base64 data URI via Vite build; decodes to plain scrollbar/box-sizing CSS, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/rsuite-no-reset-rtl.min.css-B0vQWI16.js | AI (source-diff): CSS inlined as base64 data URI via Vite build; decodes to plain RSuite theme CSS, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/rsuite-no-reset-rtl.min-af106e5c.js | AI (source-diff): Base64-encoded CSS theme data URI in minified RSuite stylesheet bundle; not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:dist/rsuite-no-reset.min-3caeeea0.js | AI (source-diff): Base64-encoded CSS theme data URI in minified RSuite stylesheet bundle; not obfuscated malicious code. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 9.0.0 | 0 / 4 | |
| 8.1.0 | 0 / 4 | |
| 8.0.0 | 0 / 4 | |
| 7.15.0 | 0 / 3 | |
| 7.14.0 | 0 / 3 | |
| 7.13.0 | 0 / 3 | |
| 7.12.0 | 0 / 3 | |
| 7.11.0 | 0 / 1 | |
| 7.10.0 | 0 / 1 | |
| 7.9.0 | 0 / 1 | |
| 7.8.0 | 0 / 0 | |
| 7.7.0 | 0 / 0 | |
| 7.6.0 | 0 / 0 |
v9.0.0
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.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.0
5 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.
Newly 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.
v7.14.0
5 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.
Newly 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.
v7.13.0
5 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.
Newly 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.
v7.12.0
5 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.
Newly 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.
v7.11.0
5 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.
Newly 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.
v7.10.0
5 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.
Newly 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.
v7.9.0
5 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.
Newly 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.
v7.8.0
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.
v7.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.