@better-auth/infra
31
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
bekacrubetter-gustavo
Keywords
better-authauthauthenticationdashboardanalyticssecurity
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual (bekacru) to GitHub Actions CI publish; consistent with official better-auth org automation. | ai | |
| provenance | missing-githead | AI (provenance): Artifact of CI publish environment change; not an obfuscation signal for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @better-auth/utils is a first-party dep from the same org; not a supply-chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across the better-auth org packages; not a risk signal for this publisher. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.3.6 | 5 / 13 | |
| 0.3.5 | 5 / 13 | |
| 0.3.4 | 5 / 13 | |
| 0.3.3 | 5 / 13 | |
| 0.3.2 | 5 / 13 | |
| 0.3.1 | 5 / 13 | |
| 0.3.0 | 5 / 13 | |
| 0.2.14 | 5 / 13 | |
| 0.2.13 | 4 / 13 | |
| 0.2.12 | 4 / 13 | |
| 0.2.11 | 4 / 13 | |
| 0.2.10 | 4 / 13 | |
| 0.2.9 | 4 / 12 | |
| 0.2.8 | 4 / 12 | |
| 0.2.7 | 4 / 12 | |
| 0.2.6 | 4 / 12 | |
| 0.2.5 | 4 / 12 | |
| 0.2.4 | 4 / 12 | |
| 0.2.3 | 4 / 12 | |
| 0.2.2 | 4 / 12 | |
| 0.2.1 | 4 / 12 | |
| 0.2.0 | 4 / 12 | |
| 0.1.14 | 4 / 11 | |
| 0.1.13 | 4 / 9 | |
| 0.1.12 | 4 / 7 | |
| 0.1.11 | 4 / 7 | |
| 0.1.10 | 4 / 7 | |
| 0.1.9 | 4 / 7 | |
| 0.1.8 | 6 / 7 | |
| 0.1.7 | 7 / 6 | |
| 0.1.6 | 7 / 6 |
v0.3.6
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.