@emeryld/manager
Interactive manager for pnpm monorepos (update/test/build/publish).
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): Spreading process.env to pass environment to a child process exec call is standard and intentional for a CLI tool. | ai |
Versions (showing 51 of 77)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 4 / 3 | |
| 1.6.0 | 4 / 3 | |
| 1.5.8 | 4 / 3 | |
| 1.5.7 | 4 / 3 | |
| 1.5.6 | 4 / 3 | |
| 1.5.5 | 4 / 3 | |
| 1.5.4 | 4 / 3 | |
| 1.5.3 | 4 / 3 | |
| 1.5.2 | 4 / 3 | |
| 1.5.1 | 4 / 3 | |
| 1.5.0 | 4 / 3 | |
| 1.4.15 | 4 / 3 | |
| 1.4.14 | 4 / 3 | |
| 1.4.12 | 4 / 3 | |
| 1.4.11 | 4 / 3 | |
| 1.4.10 | 4 / 3 | |
| 1.4.9 | 4 / 3 | |
| 1.4.8 | 4 / 3 | |
| 1.4.7 | 4 / 3 | |
| 1.4.6 | 4 / 3 | |
| 1.4.5 | 4 / 3 | |
| 1.4.4 | 4 / 3 | |
| 1.4.3 | 4 / 3 | |
| 1.4.2 | 4 / 3 | |
| 1.4.1 | 4 / 3 | |
| 1.4.0 | 4 / 3 | |
| 1.3.1 | 3 / 3 | |
| 1.3.0 | 3 / 3 | |
| 1.2.0 | 3 / 3 | |
| 1.1.0 | 3 / 3 | |
| 1.0.1 | 3 / 3 | |
| 1.0.0 | 3 / 3 | |
| 0.8.2 | 3 / 3 | |
| 0.8.1 | 3 / 3 | |
| 0.8.0 | 3 / 3 | |
| 0.7.10 | 3 / 3 | |
| 0.7.9 | 3 / 3 | |
| 0.7.8 | 3 / 3 | |
| 0.7.7 | 3 / 3 | |
| 0.7.6 | 3 / 3 | |
| 0.7.5 | 3 / 3 | |
| 0.7.4 | 3 / 3 | |
| 0.7.3 | 3 / 3 | |
| 0.7.2 | 3 / 3 | |
| 0.7.1 | 3 / 3 | |
| 0.7.0 | 3 / 3 | |
| 0.6.7 | 3 / 3 | |
| 0.6.6 | 3 / 3 | |
| 0.6.5 | 3 / 3 | |
| 0.6.4 | 3 / 3 | |
| 0.6.3 | 3 / 3 |
v1.6.1
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.15
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.14
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.12
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.11
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.10
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.9
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.8
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.7
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.10
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.9
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
2 findingsSpreading entire process.env into an object — may capture all secrets 34 | nodeArgs = ['--import', registerImport, sourceEntry, ...args] 35 | execOptions = { > 36 | env: { ...process.env, TS_NODE_PROJECT: tsconfigPath }, 37 | stdio: 'inherit', 38 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.