@vc-shell/create-vc-app
Application scaffolding
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/templates/standalone/_yarn/releases/yarn-4.9.1.cjs | AI (source-diff): Yarn Berry CJS bundle legitimately contains network and exec code; not malware. | ai | |
| source-diff | obfuscated-file:dist/templates/host-app/_yarn/releases/yarn-4.9.1.cjs | AI (source-diff): Official Yarn Berry release binary; minified by design and expected in zero-install scaffolding templates. | ai | |
| source-diff | net-exec-file:dist/templates/host-app/_yarn/releases/yarn-4.9.1.cjs | AI (source-diff): Yarn Berry CJS bundle legitimately contains network and exec code; not malware. | ai | |
| source-diff | obfuscated-file:dist/templates/standalone/_yarn/releases/yarn-4.9.1.cjs | AI (source-diff): Same Yarn Berry release binary in standalone template; minified by design. | ai | |
| phantom-deps | phantom-dep:vite | AI (phantom-deps): Build tool referenced in vite build script; legitimate dev dependency. | ai | |
| phantom-deps | phantom-dep:vite-plugin-dts | AI (phantom-deps): Build plugin referenced in vite config; legitimate dev dependency. | ai | |
| phantom-deps | phantom-dep:magicast | AI (phantom-deps): Config manipulation tool used in build; legitimate dev dependency. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit dependency; stable across versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.0.6 | 8 / 7 | |
| 2.0.5 | 8 / 7 | |
| 2.0.4 | 8 / 7 | |
| 2.0.3 | 8 / 7 | |
| 2.0.2 | 8 / 7 | |
| 2.0.1 | 8 / 7 | |
| 2.0.0 | 8 / 7 | |
| 1.2.3 | 6 / 6 | |
| 1.2.2 | 6 / 6 | |
| 1.2.1 | 6 / 6 | |
| 1.2.0 | 6 / 6 |
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andrew.kubyshkin) than the most recent previously approved version (virto) on 2026-05-25, but andrew.kubyshkin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.