@mongodb-js/saslprep
SASLprep: Stringprep Profile for User Names and Passwords, rfc4013
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 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.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.