← Home

@mongodb-js/signing-utils

npm Repository Homepage

Utilities for signing packages in CI with Garasign.

15
Versions
SSPL
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): mcasimir_mdb appears to be a renamed account of mcasimir within MongoDB org; not an external takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Paired with maintainer-added for same person (account rename); not a hostile removal. ai
bogus-package bogus-package AI (bogus-package): MongoDB devtools monorepo packages share templated names by design; not spam. ai
phantom-deps phantom-dep:@types/ssh2 AI (phantom-deps): @types/ssh2 is a runtime dep here (type stubs bundled with ssh2 usage); phantom-dep false positive for this package. ai

Versions (showing 15 of 15)

Version Deps Published
0.5.11 3 / 17
0.5.10 3 / 17
0.5.9 3 / 17
0.5.8 3 / 17
0.5.7 3 / 17
0.5.6 3 / 17
0.5.5 3 / 17
0.5.4 3 / 17
0.5.3 3 / 17
0.5.0 3 / 17
0.4.4 3 / 17
0.4.3 3 / 17
0.4.2 3 / 17
0.4.1 3 / 17
0.4.0 3 / 17

v0.5.11

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.

v0.5.10

1 finding
LOW No provenance attestation provenance

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

v0.5.9

1 finding
LOW No provenance attestation provenance

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

v0.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.

v0.5.7

1 finding
LOW No provenance attestation provenance

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

v0.5.6

1 finding
LOW No provenance attestation provenance

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

v0.5.5

1 finding
LOW No provenance attestation provenance

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

v0.5.4

1 finding
LOW No provenance attestation provenance

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

v0.5.3

1 finding
LOW No provenance attestation provenance

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

v0.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.

v0.4.4

1 finding
LOW No provenance attestation provenance

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

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

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.

v0.4.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.