← Home

@mionjs/devtools

npm Repository Homepage

Development tooling for mion (ESLint plugin and Vite plugin).

4
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ma-jerez

Keywords

typescripteslintviteplugincodegenAOTmion

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Dev tooling package; lack of provenance is common and not a disqualifier here. ai
semgrep semgrep:env-spread AI (semgrep): Spreading process.env into fork() options is standard dev-tool pattern; no secret exfiltration risk. ai
semgrep semgrep:new-function-constructor AI (semgrep): Hardcoded string probing import.meta.resolve availability; not arbitrary input execution. ai
phantom-deps phantom-dep:vite-node AI (phantom-deps): Listed as runtime dependency; used via CLI invocation (fork), not direct import. ai
phantom-deps phantom-dep:vite-plugin-dts AI (phantom-deps): Used in vite config files at build time, not directly imported in source. ai

Versions (showing 4 of 4)

Version Deps Published
0.8.8 5 / 1
0.8.7 5 / 1
0.8.6 5 / 1
0.8.4 5 / 1

v0.8.8

2 findings
HIGH env-spread: src/vite-plugin/aotCacheGenerator.ts:95 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/MionKit/mion/blob/a92a438011336a078d394b75054422f3a56f8468/src/vite-plugin/aotCacheGenerator.ts#L95 93 | // 'serve' mode tells platform adapters to proceed with server.listen() 94 | child = fork(viteNodePath, [...viteConfigArgs, startScript, ...(serverConfig.args || [])], { > 95 | env: { 96 | ...process.env, 97 | ...serverConfig.env,

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.