@vef-framework-react/dev
Dev tools 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/code-generation/dictionary/core.cjs | AI (source-diff): File is minified CJS bundle output (rolldown/tsup), not obfuscated; content is benign dictionary key code generation logic. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Convention-loaded Babel plugin; stable for framework packages. | ai | |
| phantom-deps | phantom-dep:@babel/traverse | AI (phantom-deps): Convention-loaded Babel plugin; stable for framework packages. | ai | |
| phantom-deps | phantom-dep:@svgr/plugin-svgo | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:@emotion/babel-plugin | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/utils | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:babel-plugin-react-compiler | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:@commitlint/config-conventional | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| phantom-deps | phantom-dep:sass-embedded | AI (phantom-deps): Config-file reference in dev framework; stable pattern. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @vef-framework-react/dev; levenshtein match to ajv is a clear false positive. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 53 / 16 | |
| 2.2.2 | 52 / 16 | |
| 2.2.1 | 52 / 16 | |
| 2.2.0 | 52 / 16 | |
| 2.1.12 | 52 / 16 | |
| 2.1.11 | 52 / 16 | |
| 2.1.9 | 52 / 16 | |
| 2.1.8 | 49 / 19 | |
| 2.1.7 | 49 / 19 | |
| 2.1.6 | 49 / 17 | |
| 2.1.5 | 49 / 17 | |
| 2.1.4 | 49 / 17 | |
| 2.1.3 | 49 / 17 | |
| 2.1.2 | 49 / 17 | |
| 2.1.1 | 49 / 17 | |
| 2.1.0 | 49 / 17 |
v2.3.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.