@vef-framework-react/shared
Shared utilities for VEF framework
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/types/constants/color-names.d.ts | AI (source-diff): Long lines are a flat array of [hex, name] color tuples in a .d.ts file — legitimate constant data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types/constants/color-palettes.d.ts | AI (source-diff): Long lines are inlined color palette objects in a .d.ts file — legitimate constant data, not obfuscation. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 16 / 2 | |
| 2.2.2 | 16 / 2 | |
| 2.2.1 | 16 / 2 | |
| 2.2.0 | 16 / 2 | |
| 2.1.12 | 16 / 2 | |
| 2.1.11 | 16 / 2 | |
| 2.1.10 | 16 / 2 | |
| 2.1.9 | 16 / 2 | |
| 2.1.8 | 16 / 2 | |
| 2.1.7 | 16 / 2 | |
| 2.1.6 | 16 / 2 | |
| 2.1.5 | 16 / 2 | |
| 2.1.4 | 16 / 2 | |
| 2.1.3 | 16 / 2 | |
| 2.1.2 | 16 / 2 | |
| 2.1.1 | 16 / 2 | |
| 2.1.0 | 16 / 2 |
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
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.
v2.1.1
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.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.