grant
1
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
simov
Keywords
oauthoauth2openidopenid-connectauthenticationauthorizationproxymiddlewarelambdaexpresskoahapifastifyawsazuregoogle-cloudvercel
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in AWS handler is standard API Gateway behavior for binary-encoded request bodies; not a malicious payload pattern for this OAuth proxy. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in oidc.js is part of standard PKCE/OIDC cryptographic operations (SHA1 hash to base64url); legitimate and expected in an OAuth library. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 4325-day history; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 5.4.24 | 3 / 24 |
v5.4.24
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.