mongodb-core Apache-2.0 51 versions

mongodb-core

npm Repository Homepage

Core MongoDB driver functionality, no bells and whistles and meant for integration not end applications

51

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

daprahamianmbroadst

Keywords

mongodbcore

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): The dynamic require is `require(__dirname + '/../../package.json').version` — a static path to the package's own JSON file, not user-controlled. This is a stable false positive for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): mbroadst (Matt Broadstone) is a known MongoDB engineer and mongodb-js org maintainer; this is a legitimate organizational maintainer transition, not a compromise.	ai	2026/04/24
semgrep	semgrep:base64-decode	AI (semgrep): Base64 decoding in scram.js is part of the standard SCRAM authentication protocol (decoding the server-provided salt). This is legitimate cryptographic code, not obfuscation.	ai	2026/04/23
semgrep	semgrep:hex-decode	AI (semgrep): Hex encoding/decoding of MongoDB ObjectIds for comparison is standard MongoDB driver functionality, not malicious payload hiding.	ai	2026/04/23

Versions (showing 51 of 159)

View all versions

Version	Deps	Published
3.2.7	4 / 13	2019-06-04
3.2.6	4 / 13	2019-05-23
3.2.5	4 / 13	2019-05-17
3.2.4	4 / 13	2019-05-08
3.2.3	4 / 13	2019-04-05
3.2.2	4 / 13	2019-03-22
3.2.1	4 / 13	2019-03-21
3.2.0	4 / 13	2019-03-21
3.1.11	4 / 13	2019-01-16
3.1.10	4 / 13	2019-01-15
3.1.9	4 / 13	2018-11-16
3.1.8	4 / 13	2018-11-05
3.1.7	4 / 13	2018-10-10
3.1.6	4 / 13	2018-10-09
3.1.5	4 / 13	2018-09-15
3.1.4	4 / 13	2018-09-14
3.1.3	4 / 13	2018-08-25
3.1.2	3 / 13	2018-08-13
3.1.1	3 / 13	2018-08-13
3.1.0	3 / 13	2018-06-27
3.0.11	2 / 10	2018-06-28
3.0.9	2 / 10	2018-06-01
3.0.8	2 / 10	2018-05-08
3.0.7	2 / 10	2018-04-17
3.0.6	2 / 10	2018-04-09
3.0.5	2 / 10	2018-03-14
3.0.4	2 / 10	2018-03-05
3.0.3	2 / 10	2018-02-23
3.0.2	2 / 10	2018-01-29
3.0.1	2 / 9	2017-12-24
3.0.0	2 / 9	2017-12-23
2.1.20	2 / 15	2018-07-19
2.1.19	2 / 15	2018-02-26
2.1.18	2 / 14	2018-01-03
2.1.17	2 / 13	2017-10-12
2.1.16	2 / 13	2017-10-11
2.1.15	2 / 13	2017-08-08
2.1.14	2 / 13	2017-07-07
2.1.13	2 / 13	2017-06-19
2.1.12	2 / 13	2017-06-02
2.1.11	2 / 13	2017-05-22
2.1.10	2 / 13	2017-04-18
2.1.9	2 / 13	2017-03-17
2.1.8	2 / 13	2017-02-13
2.1.7	2 / 13	2017-01-24
2.1.6	2 / 13	2017-01-13
2.1.5	2 / 13	2017-01-11
2.1.4	2 / 13	2017-01-03
2.1.3	2 / 13	2017-01-03
2.1.2	2 / 13	2016-12-10
2.1.1	2 / 13	2016-12-08

v3.2.7

1 finding

LOW No provenance attestation provenance

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

v3.2.6

1 finding

LOW No provenance attestation provenance

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

v3.2.5

2 findings

HIGH Publisher changed: mbroadst → daprahamian (on 2019-05-17) provenance

This version was published by a different npm account than previous versions on 2019-05-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.2.4

1 finding

LOW No provenance attestation provenance

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

v3.2.3

1 finding

LOW No provenance attestation provenance

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

v3.2.2

1 finding

LOW No provenance attestation provenance

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.11

1 finding

LOW No provenance attestation provenance

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

v3.1.10

1 finding

LOW No provenance attestation provenance

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

v3.1.9

1 finding

LOW No provenance attestation provenance

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

v3.1.8

1 finding

LOW No provenance attestation provenance

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

v3.1.7

1 finding

LOW No provenance attestation provenance

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

v3.1.6

1 finding

LOW No provenance attestation provenance

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

v3.1.5

1 finding

LOW No provenance attestation provenance

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

v3.1.4

1 finding

LOW No provenance attestation provenance

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

v3.1.3

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.0

2 findings

HIGH Publisher changed: daprahamian → mbroadst (on 2018-06-27) provenance

This version was published by a different npm account than previous versions on 2018-06-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.0.11

1 finding

LOW No provenance attestation provenance

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

v3.0.9

2 findings

HIGH Publisher changed: daprahamian → mbroadst (on 2018-06-01) provenance

This version was published by a different npm account than previous versions on 2018-06-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.0.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mbroadst → daprahamian (on 2018-05-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-05-08. This could indicate a legitimate maintainer transition or an account compromise.

v3.0.7

1 finding

LOW No provenance attestation provenance

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

v3.0.6

1 finding

LOW No provenance attestation provenance

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

v3.0.5

1 finding

LOW No provenance attestation provenance

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

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mbroadst → daprahamian (on 2018-02-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-23. This could indicate a legitimate maintainer transition or an account compromise.

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.1.20

1 finding

LOW No provenance attestation provenance

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

v2.1.19

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: daprahamian → mbroadst (on 2018-02-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-26. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.18

1 finding

LOW No provenance attestation provenance

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

v2.1.17

1 finding

LOW No provenance attestation provenance

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

v2.1.16

1 finding

LOW No provenance attestation provenance

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

v2.1.15

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: christkv → mbroadst (on 2017-08-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-08-08. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.14

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: christkv → mbroadst (on 2017-07-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-07-07. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.13

1 finding

LOW No provenance attestation provenance

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

v2.1.12

1 finding

LOW No provenance attestation provenance

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

v2.1.11

1 finding

LOW No provenance attestation provenance

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

v2.1.10

1 finding

LOW No provenance attestation provenance

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

v2.1.9

1 finding

LOW No provenance attestation provenance

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

v2.1.8

1 finding

LOW No provenance attestation provenance

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

v2.1.7

1 finding

LOW No provenance attestation provenance

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

v2.1.6

1 finding

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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