@nativescript/vite
Vite for NativeScript
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Standard subprocess env-passing pattern in a build tool; not exfiltration. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-specified external config files; expected build-tool behavior. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): CJS module loader shim for ESM context; input is user-controlled config, not remote data. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Scoped package @nativescript/vite is not a typosquat of vitest; Levenshtein match is spurious. | ai | |
| phantom-deps | phantom-dep:sass | AI (phantom-deps): sass is a peer/optional dep referenced in config; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@angular/build | AI (phantom-deps): Framework-scoped package loaded by convention; false positive for this build tool. | ai | |
| phantom-deps | phantom-dep:@angular-devkit/build-angular | AI (phantom-deps): Angular build tooling loaded by convention; false positive for this build tool. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 22 / 2 | |
| 2.0.2 | 22 / 2 | |
| 2.0.1 | 22 / 2 | |
| 2.0.0 | 22 / 2 | |
| 1.0.5 | 21 / 2 | |
| 1.0.4 | 21 / 2 | |
| 1.0.3 | 21 / 2 | |
| 1.0.2 | 21 / 2 | |
| 1.0.1 | 21 / 2 | |
| 1.0.0 | 21 / 2 | |
| 0.0.2 | 21 / 2 |
v2.0.3
2 findingsSpreading entire process.env into an object — may capture all secrets 242 | const result = spawnSync(process.execPath, [vueTscBinPath, '--noEmit', '--pretty', '-p', tsConfigPath, '--mo 243 | cwd: process.cwd(), > 244 | env: { ...process.env, FORCE_COLOR: '1' }, 245 | encoding: 'utf8', 246 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.