← Home

mongodb-log-writer

npm Repository Homepage
15
Versions
—
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

mongodb-js-useralexander_schrollmbroadsthswolffsatyasinhajeff-allen-mongojonathan.balsanomongodb-buildjack.weirkristina.stefanojarjeeshaketbabydevtoolsbotgribnoysupmutukrishmongo-jdariakpaddaleaxnbbeekendbx-nodenirinchevpearsb1mcasimir_mdb

Keywords

mongodbloglogv2

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): mcasimir_mdb is a renamed/migrated MongoDB org account; stable pattern for this package. ai
maintainer-change maintainer-removed AI (maintainer-change): mcasimir removal corresponds to account rename to mcasimir_mdb within MongoDB org. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy consistent with stable library; no code changes and official MongoDB org ownership. ai

Versions (showing 15 of 15)

Version Deps Published
2.5.13 1 / 18
2.5.12 1 / 18
2.5.11 1 / 18
2.5.10 1 / 18
2.5.9 1 / 18
2.5.8 1 / 18
2.5.7 1 / 18
2.5.6 1 / 18
2.5.5 1 / 18
2.5.4 1 / 18
2.5.3 1 / 18
2.5.0 1 / 18
2.4.4 1 / 18
2.4.3 1 / 18
2.4.2 1 / 18

v2.5.13

1 finding
LOW No provenance attestation provenance

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

v2.5.12

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.

v2.5.11

1 finding
LOW No provenance attestation provenance

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

v2.5.10

1 finding
LOW No provenance attestation provenance

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

v2.5.9

1 finding
LOW No provenance attestation provenance

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

v2.5.8

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.

v2.5.7

1 finding
LOW No provenance attestation provenance

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

v2.5.6

1 finding
LOW No provenance attestation provenance

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

v2.5.5

1 finding
LOW No provenance attestation provenance

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

v2.5.4

1 finding
LOW No provenance attestation provenance

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

v2.5.3

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.4

1 finding
LOW No provenance attestation provenance

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

v2.4.3

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. Only ~12% of npm packages have provenance, so this is common but not ideal.