@zero-server/auth
JWT, sessions, OAuth, authorize, MFA stack.
14
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
molex222
Keywords
zero-serverzero-serverauth
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is typical for this publisher/package family; not a risk signal here. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Fires on Buffer.from(hash, 'hex') in TOTP comparison — standard crypto pattern, not payload hiding. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 1 / 0 | |
| 1.0.2 | 1 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 | |
| 0.9.10 | 1 / 0 | |
| 0.9.9 | 1 / 0 | |
| 0.9.8 | 1 / 0 | |
| 0.9.7 | 1 / 0 | |
| 0.9.6 | 1 / 0 | |
| 0.9.5 | 1 / 0 | |
| 0.9.3 | 1 / 0 | |
| 0.9.2 | 1 / 0 | |
| 0.9.1 | 1 / 0 | |
| 0.9.0 | 1 / 0 |
v1.1.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.