← Home

@mongodb-js/saslprep

SASLprep: Stringprep Profile for User Names and Passwords, rfc4013

26
Versions
MIT
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

saslsaslprepstringpreprfc40134013

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:sparse-bitfield AI (dependencies): sparse-bitfield is a well-known stable package appropriate for Unicode code-point bitfield storage in a SASLprep implementation; not a risk for this package. ai
provenance no-provenance AI (provenance): MongoDB JS packages are published via devtoolsbot automation; lack of Sigstore provenance is consistent across the org and not a meaningful risk signal here. ai

Versions (showing 26 of 26)

Version Deps Published
1.4.12 1 / 18
1.4.11 1 / 18
1.4.10 1 / 18
1.4.9 1 / 18
1.4.8 1 / 18
1.4.7 1 / 18
1.4.6 1 / 18
1.4.5 1 / 18
1.4.4 1 / 18
1.4.3 1 / 18
1.4.0 1 / 18
1.3.2 1 / 18
1.3.1 1 / 18
1.3.0 1 / 18
1.2.2 1 / 18
1.2.1 1 / 18
1.2.0 1 / 18
1.1.9 1 / 18
1.1.8 1 / 18
1.1.7 1 / 18
1.1.6 1 / 18
1.1.5 1 / 18
1.1.4 1 / 18
1.1.3 1 / 18
1.1.1 1 / 18
1.1.0 1 / 18

v1.4.12

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: devtoolsbot → gribnoysup (on 2026-06-30, known maintainer) provenance

This version was published by a different npm account (gribnoysup) than the most recent previously approved version (devtoolsbot) on 2026-06-30, but gribnoysup is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.