@genesislcap/rapid-design-system
Rapid Design System
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/dts/flexlayout-react-theme/flexlayout-react-theme.generated.d.ts | AI (source-diff): Generated .d.ts file containing a vendored CSS string; long lines are expected and benign for this package. | ai | |
| source-diff | obfuscated-file:dist/dts/_config/tokens/error-palette.d.ts | AI (source-diff): Long-line .d.ts files are normal for TypeScript token declarations with deeply nested generics; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/dts/_config/tokens/success-palette.d.ts | AI (source-diff): Same pattern: generated .d.ts with long generic type chains, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/dts/_config/tokens/warning-palette.d.ts | AI (source-diff): Same pattern: generated .d.ts with long generic type chains, not obfuscated code. | ai |
Versions (showing 51 of 759)
| Version | Deps | Published |
|---|---|---|
| 15.2.0 | 9 / 9 | |
| 15.1.0 | 9 / 9 | |
| 15.0.0 | 9 / 9 | |
| 14.501.0 | 9 / 9 | |
| 14.500.0 | 9 / 9 | |
| 14.499.0 | 9 / 9 | |
| 14.498.0 | 9 / 9 | |
| 14.497.0 | 9 / 9 | |
| 14.496.1 | 9 / 9 | |
| 14.496.0 | 9 / 9 | |
| 14.495.0 | 9 / 9 | |
| 14.494.0 | 9 / 9 | |
| 14.493.0 | 9 / 9 | |
| 14.492.1 | 9 / 9 | |
| 14.492.0 | 9 / 9 | |
| 14.491.1 | 9 / 9 | |
| 14.491.0 | 9 / 9 | |
| 14.490.0 | 9 / 9 | |
| 14.489.0 | 9 / 9 | |
| 14.488.2 | 9 / 9 | |
| 14.488.1 | 9 / 9 | |
| 14.488.0 | 9 / 9 | |
| 14.487.0 | 9 / 9 | |
| 14.486.1 | 9 / 9 | |
| 14.486.0 | 9 / 9 | |
| 14.485.0 | 9 / 8 | |
| 14.484.2 | 9 / 8 | |
| 14.484.1 | 9 / 8 | |
| 14.484.0 | 9 / 8 | |
| 14.483.2 | 9 / 8 | |
| 14.483.1 | 9 / 8 | |
| 14.483.0 | 9 / 8 | |
| 14.482.1 | 9 / 8 | |
| 14.482.0 | 9 / 8 | |
| 14.481.1 | 9 / 8 | |
| 14.481.0 | 9 / 8 | |
| 14.480.0 | 9 / 8 | |
| 14.479.0 | 9 / 8 | |
| 14.478.0 | 9 / 8 | |
| 14.477.0 | 9 / 8 | |
| 14.476.0 | 9 / 8 | |
| 14.475.0 | 9 / 8 | |
| 14.474.1 | 9 / 8 | |
| 14.474.0 | 9 / 8 | |
| 14.473.0 | 9 / 8 | |
| 14.472.2 | 9 / 8 | |
| 14.472.1 | 9 / 8 | |
| 14.472.0 | 9 / 8 | |
| 14.471.0 | 9 / 7 | |
| 14.470.0 | 9 / 7 | |
| 14.469.0 | 9 / 7 |
v15.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.501.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.500.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.499.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.498.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.497.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.496.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.496.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.495.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.494.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.493.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.492.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.492.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.491.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.491.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.490.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.489.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.488.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.488.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.488.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.487.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.486.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.486.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.485.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.484.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.484.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.484.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.483.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.483.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.483.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.482.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.482.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.481.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.481.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.480.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.479.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.478.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.477.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.
v14.476.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.
v14.475.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.
v14.474.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.
v14.474.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.
v14.473.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.
v14.472.2
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.
v14.472.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.