@jsreport/jsreport-authentication
5
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
pofiderbjrmatos
Keywords
jsreportauthentication
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:password-hash | AI (dependencies): Stable, purpose-appropriate dependency for an auth extension; no known advisories. | ai | |
| dependencies | unvetted-dep:client-sessions | AI (dependencies): Well-known Mozilla session library; appropriate for auth plugin, no known advisories. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 9 / 9 | |
| 4.3.0 | 9 / 9 | |
| 4.2.3 | 9 / 9 | |
| 4.2.2 | 9 / 9 | |
| 4.2.1 | 9 / 9 |
v4.2.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.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.