@better-auth/cli
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @better-auth/cli is unrelated to joi; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:pg | AI (phantom-deps): CLI loads database adapters optionally; pg is a supported adapter loaded by convention. | ai | |
| phantom-deps | phantom-dep:jiti | AI (phantom-deps): Used for dynamic config loading at runtime, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:prisma | AI (phantom-deps): Optional adapter dependency loaded by convention in CLI context. | ai | |
| phantom-deps | phantom-dep:tinyexec | AI (phantom-deps): Utility used indirectly; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:@types/pg | AI (phantom-deps): Type-only dependency for pg adapter; framework-scoped, expected pattern. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Used for transpilation support; loaded by convention in CLI build pipeline. | ai | |
| phantom-deps | phantom-dep:get-tsconfig | AI (phantom-deps): Config resolution utility; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:@prisma/client | AI (phantom-deps): Optional Prisma adapter dependency loaded by convention. | ai | |
| phantom-deps | phantom-dep:better-sqlite3 | AI (phantom-deps): Optional SQLite adapter loaded by convention in CLI context. | ai | |
| phantom-deps | phantom-dep:@better-auth/core | AI (phantom-deps): Same-org package; expected peer dependency pattern for better-auth CLI. | ai |
Versions (showing 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 1.4.22 | 24 / 9 | |
| 1.4.21 | 24 / 9 | |
| 1.4.20 | 24 / 9 | |
| 1.4.19 | 24 / 9 | |
| 1.4.18 | 24 / 9 | |
| 1.4.17 | 24 / 9 | |
| 1.4.16 | 24 / 9 | |
| 1.4.15 | 24 / 9 | |
| 1.4.14 | 24 / 9 | |
| 1.4.13 | 24 / 9 | |
| 1.4.12 | 24 / 9 | |
| 1.4.11 | 24 / 9 | |
| 1.4.10 | 24 / 9 | |
| 1.4.9 | 24 / 9 | |
| 1.4.8 | 24 / 9 | |
| 1.4.7 | 24 / 9 | |
| 1.4.6 | 24 / 9 | |
| 1.4.5 | 24 / 9 | |
| 1.4.4 | 27 / 8 | |
| 1.4.3 | 27 / 8 | |
| 1.4.2 | 27 / 8 | |
| 1.4.1 | 27 / 8 | |
| 1.4.0 | 27 / 8 | |
| 1.3.34 | 26 / 4 | |
| 1.3.33 | 26 / 4 | |
| 1.3.32 | 26 / 4 | |
| 1.3.31 | 26 / 4 | |
| 1.3.30 | 26 / 4 | |
| 1.3.29 | 26 / 4 | |
| 1.3.28 | 26 / 4 | |
| 1.3.27 | 26 / 4 | |
| 1.3.26 | 26 / 4 | |
| 1.3.25 | 26 / 4 | |
| 1.3.24 | 25 / 4 | |
| 1.3.23 | 25 / 4 | |
| 1.3.22 | 25 / 4 | |
| 1.3.18 | 25 / 4 | |
| 1.3.17 | 25 / 4 | |
| 1.3.16 | 25 / 4 | |
| 1.3.15 | 25 / 4 | |
| 1.3.14 | 24 / 3 | |
| 1.3.13 | 24 / 3 | |
| 1.3.12 | 24 / 3 | |
| 1.3.11 | 24 / 3 | |
| 1.3.10 | 24 / 3 | |
| 1.3.9 | 24 / 3 | |
| 1.3.8 | 24 / 3 | |
| 1.3.7 | 23 / 5 | |
| 1.3.6 | 23 / 5 | |
| 1.3.5 | 23 / 5 | |
| 1.3.4 | 24 / 5 |
v1.4.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.