← Home

@mongosh/snippet-manager

npm Repository Homepage

MongoDB Shell Snippet Manager

10
Versions
Apache-2.0
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

devtoolsbotaddaleaxalexander_schrollnirinchevmcasimir_mdb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Intentional pattern: passes process.env + one extra var to child process; standard for mongosh subprocess invocation. ai

Versions (showing 10 of 10)

Version Deps Published
5.1.9 8 / 9
5.1.7 9 / 8
5.1.6 9 / 8
5.1.4 9 / 8
5.1.0 9 / 8
5.0.1 9 / 8
5.0.0 9 / 8
3.29.1 9 / 9
3.29.0 9 / 9
3.28.0 9 / 9

v5.1.9

2 findings
HIGH env-spread: lib/snippet-manager.js:355 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/mongodb-js/mongosh/blob/d5a0d964b21e3dc651a3a8391f21c87117e74514/lib/snippet-manager.js#L355 353 | const proc = (0, cross_spawn_1.spawn)(cmd, args, { 354 | cwd: this.installdir, > 355 | env: { ...process.env, MONGOSH_RUN_NODE_SCRIPT: '1' }, 356 | stdio: 'pipe', 357 | });

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.

v5.1.7

2 findings
HIGH env-spread: lib/snippet-manager.js:356 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/mongodb-js/mongosh/blob/5657df58a88eaa591e78fbb9052f9feaa0d4b8e8/lib/snippet-manager.js#L356 354 | const proc = (0, cross_spawn_1.spawn)(cmd, args, { 355 | cwd: this.installdir, > 356 | env: { ...process.env, MONGOSH_RUN_NODE_SCRIPT: '1' }, 357 | stdio: 'pipe', 358 | });

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.

v5.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.0

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.

v3.29.1

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.

v3.29.0

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.

v3.28.0

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.