@justprove/mobilevc
Claude Code mobile workspace launcher with precompiled MobileVC backend binaries.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env to pass to a spawned child process is standard and expected for a CLI launcher tool. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI launcher that spawns precompiled binaries; child_process use is core to the package's stated purpose. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.2.14 | 1 / 0 | |
| 0.2.11 | 1 / 0 | |
| 0.2.10 | 1 / 0 | |
| 0.2.9 | 1 / 0 | |
| 0.2.8 | 1 / 0 | |
| 0.2.7 | 1 / 0 | |
| 0.2.6 | 1 / 0 | |
| 0.2.5 | 1 / 0 | |
| 0.2.4 | 1 / 0 | |
| 0.2.2 | 1 / 0 | |
| 0.2.0 | 1 / 0 | |
| 0.1.18 | 1 / 0 | |
| 0.1.17 | 1 / 0 | |
| 0.1.16 | 1 / 0 | |
| 0.1.15 | 1 / 0 | |
| 0.1.14 | 1 / 0 | |
| 0.1.13 | 1 / 0 | |
| 0.1.12 | 1 / 0 | |
| 0.1.11 | 1 / 0 | |
| 0.1.10 | 1 / 0 | |
| 0.1.9 | 1 / 0 | |
| 0.1.8 | 1 / 0 | |
| 0.1.7 | 1 / 0 | |
| 0.1.6 | 1 / 0 | |
| 0.1.5 | 1 / 0 | |
| 0.1.3 | 1 / 0 | |
| 0.1.2 | 1 / 0 | |
| 0.1.1 | 1 / 0 | |
| 0.1.0 | 1 / 0 |
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
2 findingsSpreading entire process.env into an object — may capture all secrets 275 | } catch (_) {} 276 | > 277 | const env = { 278 | ...process.env, 279 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
2 findingsSpreading entire process.env into an object — may capture all secrets 255 | } catch (_) {} 256 | > 257 | const env = { 258 | ...process.env, 259 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
2 findingsSpreading entire process.env into an object — may capture all secrets 255 | } catch (_) {} 256 | > 257 | const env = { 258 | ...process.env, 259 | PORT: String(config.port),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.