← Home

@mongosh/node-runtime-worker-thread

npm Repository Homepage

MongoDB shell runtime that lives in a worker thread

13
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
source-diff encoded-string-file:dist/worker-runtime.js AI (source-diff): Webpack-bundled output; long encoded strings are normal minification artifacts for this package. ai
dependencies unvetted-dep:interruptor AI (dependencies): Known mongosh runtime dependency for thread interruption; stable across versions. ai
dependencies unvetted-dep:@mongosh/shell-bson AI (dependencies): First-party mongosh monorepo package; stable dependency across versions. ai
bogus-package bogus-package AI (bogus-package): Mongosh monorepo internal package; sparse README/keywords are expected for workspace components. ai
phantom-deps phantom-dep:system-ca AI (phantom-deps): system-ca is a declared runtime dep; phantom-dep heuristic misfires for this package. ai

Versions (showing 13 of 13)

Version Deps Published
5.2.13 3 / 17
5.2.11 3 / 17
5.2.7 3 / 17
5.2.5 3 / 17
5.2.4 2 / 17
5.2.2 2 / 17
5.0.3 2 / 17
5.0.2 2 / 17
5.0.1 2 / 17
5.0.0 2 / 17
3.3.34 2 / 17
3.3.33 3 / 16
3.3.32 3 / 16

v5.2.13

1 finding
LOW No provenance attestation provenance

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

v5.2.11

2 findings
HIGH Long encoded string in modified file: dist/worker-runtime.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v5.2.4

1 finding
LOW No provenance attestation provenance

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

v5.2.2

1 finding
LOW No provenance attestation provenance

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

v5.0.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.

v5.0.2

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.

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. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.34

1 finding
LOW No provenance attestation provenance

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

v3.3.33

1 finding
LOW No provenance attestation provenance

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

v3.3.32

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.