@proofkit/better-auth
FileMaker adapter for Better Auth
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is backed by SLSA provenance attestation; legitimate CI/CD automation. | ai | |
| phantom-deps | phantom-dep:vite | AI (phantom-deps): vite is a build-time dep used in config files, not directly imported in source; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): CLI tool dependency used in config/build context; stable false positive. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Config utility; stable false positive for this package. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Filters process.env by prefix to separate public/private SvelteKit env vars — expected behavior for this adapter. | ai | |
| phantom-deps | phantom-dep:@proofkit/fmdapi | AI (phantom-deps): Same org scope; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tanstack/vite-config | AI (phantom-deps): Build config dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI framework; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 13 / 7 | |
| 0.4.0 | 13 / 7 | |
| 0.3.0 | 15 / 7 | |
| 0.2.4 | 16 / 6 | |
| 0.2.3 | 16 / 6 | |
| 0.2.2 | 17 / 6 | |
| 0.2.1 | 17 / 6 | |
| 0.2.0 | 16 / 6 | |
| 0.1.0 | 16 / 5 |
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.