mongodb
The official MongoDB driver for Node.js
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): christkv is the original MongoDB driver author who has since transitioned out. Maintainer rotation is expected for this long-lived official MongoDB package. | ai | |
| provenance | publisher-changed | AI (provenance): daprahamian is a long-standing MongoDB org contributor (2980 days, 70 approved packages). Publisher transitions are expected for this official MongoDB package over its 8+ year lifespan. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() usage is in bundled test dependency deps/nodeunit/deps/json2.js — a legacy JSON polyfill. Not in the main driver code and not a supply-chain risk. | ai | |
| install-scripts | install-script:install | AI (install-scripts): The install script (node install.js) is a long-standing part of the mongodb package for native binding setup, not a new or suspicious addition. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require() is in deps/nodeunit test framework code, not in the main mongodb driver. Standard test runner pattern. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is in deps/nodeunit/deps/ejs.js, a bundled test template engine. Standard pattern for template compilation, not in production driver code. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in SCRAM auth (salt handling) is standard cryptographic practice for a MongoDB driver; not a malicious payload indicator. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding used for ObjectId comparison is standard driver functionality; not a malicious payload indicator. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get/set used for generic options object cloning in encrypter.js — legitimate JavaScript pattern, not obfuscation. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 169.254.169.254 is the Azure IMDS link-local address for managed identity token retrieval — standard Azure SDK pattern. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Spawns 'npm run build:dts' in prepare script for development builds only; benign build tooling. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): etc/prepare.js uses child_process only to run npm build:dts when src/ exists — standard build tooling, not runtime code. | ai | |
| semgrep | semgrep:silent-process-exec-var | AI (semgrep): Same mongocryptd spawn as above; detached process is required for CSFLE daemon lifecycle management. | ai | |
| semgrep | semgrep:silent-process-exec | AI (semgrep): mongocryptd_manager.js spawns the MongoDB CSFLE daemon as a detached process — documented, expected behavior for client-side encryption support. | ai |
Versions (showing 51 of 77)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 3 / 51 | |
| 7.1.1 | 3 / 50 | |
| 7.1.0 | 3 / 50 | |
| 7.0.0 | 3 / 49 | |
| 6.21.0 | 3 / 50 | |
| 6.20.0 | 3 / 50 | |
| 6.19.0 | 3 / 50 | |
| 6.18.0 | 3 / 50 | |
| 6.17.0 | 3 / 50 | |
| 6.16.0 | 3 / 50 | |
| 6.15.0 | 3 / 50 | |
| 6.14.2 | 3 / 50 | |
| 6.14.1 | 3 / 50 | |
| 6.14.0 | 3 / 50 | |
| 6.13.1 | 3 / 50 | |
| 6.13.0 | 3 / 50 | |
| 6.12.0 | 3 / 50 | |
| 6.11.0 | 3 / 50 | |
| 6.10.0 | 3 / 50 | |
| 6.9.0 | 3 / 50 | |
| 6.8.2 | 3 / 52 | |
| 6.8.1 | 3 / 52 | |
| 6.8.0 | 3 / 52 | |
| 6.7.0 | 3 / 52 | |
| 6.6.2 | 3 / 53 | |
| 6.6.1 | 3 / 53 | |
| 6.6.0 | 3 / 53 | |
| 6.5.0 | 3 / 51 | |
| 6.4.0 | 3 / 51 | |
| 6.3.0 | 3 / 50 | |
| 6.2.0 | 3 / 50 | |
| 6.1.0 | 3 / 50 | |
| 6.0.0 | 3 / 50 | |
| 5.9.2 | 3 / 45 | |
| 5.9.1 | 3 / 45 | |
| 5.9.0 | 3 / 45 | |
| 5.8.1 | 3 / 45 | |
| 5.8.0 | 3 / 45 | |
| 4.17.2 | 3 / 46 | |
| 4.17.1 | 3 / 46 | |
| 4.17.0 | 3 / 46 | |
| 3.7.4 | 6 / 33 | |
| 3.7.3 | 6 / 33 | |
| 3.7.2 | 6 / 33 | |
| 3.7.1 | 6 / 33 | |
| 3.7.0 | 6 / 33 | |
| 3.6.12 | 6 / 33 | |
| 3.6.11 | 6 / 33 | |
| 3.6.10 | 6 / 33 | |
| 3.5.11 | 6 / 24 | |
| 3.5.10 | 6 / 24 |
v7.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-23. This could indicate a legitimate maintainer transition or an account compromise.
v5.8.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-21. This could indicate a legitimate maintainer transition or an account compromise.
v4.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.17.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-23. This could indicate a legitimate maintainer transition or an account compromise.
v4.17.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-17. This could indicate a legitimate maintainer transition or an account compromise.
v3.7.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-06-21. This could indicate a legitimate maintainer transition or an account compromise.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-10-05. This could indicate a legitimate maintainer transition or an account compromise.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-05. This could indicate a legitimate maintainer transition or an account compromise.
v3.6.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-07-06. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.