← Home

@mongosh/cli-repl

npm Repository Homepage

MongoDB Shell CLI REPL Package

26
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

devtoolsbotaddaleaxalexander_schrollnirinchevmcasimir_mdb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Spreading process.env in smoke-tests.js is standard test harness behavior for a CLI tool. ai
semgrep semgrep:eval-usage AI (semgrep): eval() is the core mechanism of a REPL; expected and intentional in node-repl-fix-history-rewrite-on-error.js. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require of builtins is a documented webpack compatibility pattern in mongosh. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in smoke-tests.js to spawn the shell binary; expected for a CLI test harness. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding is used for TLS certificate thumbprint lookup; legitimate and documented use. ai

Versions (showing 26 of 26)

Version Deps Published
2.9.2 34 / 17
2.9.1 34 / 17
2.8.3 34 / 17
2.8.2 32 / 17
2.8.1 32 / 17
2.7.0 32 / 17
2.6.0 32 / 17
2.5.10 33 / 18
2.5.9 32 / 18
2.5.8 31 / 18
2.5.7 31 / 18
2.5.6 31 / 18
2.5.5 31 / 18
2.5.3 31 / 18
2.5.2 31 / 18
2.5.1 31 / 18
2.5.0 31 / 18
2.4.2 31 / 18
2.4.0 31 / 18
2.3.9 31 / 18
2.3.8 31 / 18
2.3.7 31 / 18
2.3.6 31 / 18
2.3.5 31 / 18
2.3.4 31 / 18
2.3.3 31 / 18

v2.9.2

1 finding
LOW No provenance attestation provenance

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

v2.9.1

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.2

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.9

1 finding
LOW No provenance attestation provenance

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

v2.3.8

1 finding
LOW No provenance attestation provenance

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

v2.3.7

1 finding
LOW No provenance attestation provenance

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

v2.3.6

1 finding
LOW No provenance attestation provenance

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

v2.3.5

1 finding
LOW No provenance attestation provenance

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

v2.3.4

1 finding
LOW No provenance attestation provenance

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

v2.3.3

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.