@vef-framework-react/core
Core features 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/cjs/storage/uploader.cjs | AI (source-diff): Minified build output of a legitimate file uploader class; not obfuscated malware. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped framework package; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 19 / 1 | |
| 2.2.2 | 19 / 1 | |
| 2.2.1 | 19 / 1 | |
| 2.2.0 | 19 / 1 | |
| 2.1.12 | 19 / 1 | |
| 2.1.11 | 19 / 1 | |
| 2.1.10 | 19 / 1 | |
| 2.1.9 | 19 / 1 | |
| 2.1.8 | 19 / 1 | |
| 2.1.7 | 19 / 1 | |
| 2.1.6 | 19 / 1 | |
| 2.1.5 | 19 / 1 | |
| 2.1.4 | 19 / 1 | |
| 2.1.3 | 19 / 1 | |
| 2.1.2 | 19 / 1 | |
| 2.1.1 | 19 / 1 | |
| 2.1.0 | 19 / 1 |
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
v2.2.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.
v2.2.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.
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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
2 findingsPackage name '@vef-framework-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
2 findingsPackage name '@vef-framework-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
2 findingsPackage name '@vef-framework-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
2 findingsPackage name '@vef-framework-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
2 findingsPackage name '@vef-framework-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
2 findingsPackage name '@vef-framework-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
2 findingsPackage name '@vef-framework-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.