@gershy/manager
TODO
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): Used in process-spawning helper to forward env to child processes; standard pattern for this package's purpose. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used on a CLI argument (process.argv) — operator-controlled input, not remote/untrusted data. Stable pattern for this CLI tool. | ai | |
| phantom-deps | phantom-dep:@gershy/util-retry | AI (phantom-deps): Same-org scoped dep; likely used transitively or in bundled output. Stable false positive for this package. | ai |
v0.0.6
3 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/manager/blob/a5e1294ba72c8a87561649e95ec1a3cf2284f9c3/cmp/cjs/main.js#L54 52 | const config = await manageFact.kid(["config.json"]).getData("json"); 53 | const proc2 = ((cmd2, opts = {}) => { > 54 | return (0, import_nodejs_proc.default)(cmd2, { cwd: import_disk.rootFact, ...opts, env: { ...process.env, ...opts. 55 | }); 56 | const githubOwner2 = { type: "org", name: "gershyNpm" };
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/manager/blob/a5e1294ba72c8a87561649e95ec1a3cf2284f9c3/cmp/esm/main.js#L31 29 | const config = await manageFact.kid(["config.json"]).getData("json"); 30 | const proc2 = ((cmd2, opts = {}) => { > 31 | return procRaw(cmd2, { cwd: rootFact, ...opts, env: { ...process.env, ...opts.env ?? {} } }); 32 | }); 33 | const githubOwner2 = { type: "org", name: "gershyNpm" };
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.