@better-auth/core
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped auth library with ESM-first exports; empty CJS main and missing repo URL are packaging style choices, not spam indicators. | ai | |
| source-diff | obfuscated-file:dist/index-Zbo6xPkd.d.mts | AI (source-diff): This is a bundled TypeScript declaration (.d.mts) file generated by tsdown. Long lines are expected in flattened type declaration bundles; content is clearly type definitions, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/index-NeeRjOR2.d.mts | AI (source-diff): This is a bundled TypeScript declaration file (.d.mts) generated by tsdown. Long lines in .d.mts files are normal for bundled type declarations, not obfuscation. Content is clearly readable type definitions. | ai | |
| source-diff | obfuscated-file:dist/index-D_XSRX55.d.mts | AI (source-diff): This is a bundled TypeScript declaration (.d.mts) file with long lines from concatenated type definitions — not obfuscated executable code. Pattern is expected for this package's build output. | ai | |
| source-diff | obfuscated-file:dist/index-zgYuzZ7O.d.mts | AI (source-diff): This is a TypeScript declaration file (.d.mts) generated by tsdown bundler. Long lines are from inlined type definitions, not obfuscated executable code. Stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/index-BHaoMSKV.d.mts | AI (source-diff): This is a bundled TypeScript declaration file (.d.mts) with long lines from concatenated type definitions — not obfuscated executable code. Pattern is stable for this build toolchain. | ai | |
| source-diff | obfuscated-file:dist/index-D6KwwQy5.d.mts | AI (source-diff): This is a TypeScript declaration file (.d.mts) containing bundled type definitions, not executable code. Long lines are from concatenated type declarations, a normal artifact of tsdown builds for this package. | ai | |
| source-diff | obfuscated-file:dist/index-1XS3AkXa.d.mts | AI (source-diff): File is a TypeScript declaration (.d.mts) with long lines due to complex generic types — not executable code. This pattern is expected for a large auth framework's bundled type declarations. | ai | |
| source-diff | obfuscated-file:dist/index-BlxTbL2l.d.mts | AI (source-diff): File is a bundled TypeScript declaration (.d.mts) with long type expressions — not executable obfuscated code. Standard output of tsdown bundler for this package. | ai | |
| source-diff | obfuscated-file:dist/index-CBdZH5fV.d.mts | AI (source-diff): This is a bundled TypeScript declaration file (.d.mts) generated by tsdown. Long lines are typical of rolled-up type definitions, not obfuscation. No executable code present. | ai | |
| source-diff | obfuscated-file:dist/index-DRwH9Qxo.d.mts | AI (source-diff): This is a bundled TypeScript declaration file (.d.mts) generated by tsdown. Long lines are a normal artifact of inlined type definitions, not obfuscation. No executable code is present. | ai | |
| source-diff | obfuscated-file:dist/index-CVLGS-cz.d.mts | AI (source-diff): This is a bundled TypeScript declaration file (.d.mts) produced by tsdown. Long lines are a known artifact of declaration bundling, not obfuscation. No runtime impact. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): False positive: the match is between the unqualified name 'core' and 'cors'. @better-auth/core is the legitimate core package of the better-auth framework, not a typosquat of the cors middleware. | ai |
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 1.6.14 | 3 / 11 | |
| 1.6.13 | 3 / 11 | |
| 1.6.12 | 3 / 11 | |
| 1.6.11 | 3 / 11 | |
| 1.6.10 | 3 / 11 | |
| 1.6.9 | 3 / 11 | |
| 1.6.8 | 3 / 11 | |
| 1.6.7 | 3 / 11 | |
| 1.6.6 | 3 / 11 | |
| 1.6.5 | 3 / 11 | |
| 1.6.4 | 3 / 11 | |
| 1.6.3 | 3 / 11 | |
| 1.6.2 | 3 / 11 | |
| 1.6.1 | 3 / 11 | |
| 1.6.0 | 3 / 11 | |
| 1.5.6 | 3 / 11 | |
| 1.5.5 | 2 / 8 | |
| 1.5.4 | 2 / 8 | |
| 1.5.3 | 2 / 8 | |
| 1.5.2 | 2 / 8 | |
| 1.5.1 | 2 / 8 | |
| 1.5.0 | 2 / 8 | |
| 1.4.22 | 2 / 7 | |
| 1.4.21 | 2 / 7 | |
| 1.4.20 | 2 / 7 | |
| 1.4.19 | 2 / 7 | |
| 1.4.18 | 2 / 7 | |
| 1.4.17 | 2 / 7 | |
| 1.4.16 | 2 / 7 | |
| 1.4.15 | 2 / 7 | |
| 1.4.14 | 2 / 7 | |
| 1.4.13 | 2 / 7 | |
| 1.4.12 | 2 / 7 | |
| 1.4.11 | 2 / 7 | |
| 1.4.10 | 2 / 7 | |
| 1.4.9 | 2 / 7 | |
| 1.4.8 | 2 / 7 | |
| 1.4.7 | 2 / 7 | |
| 1.4.6 | 2 / 7 | |
| 1.4.5 | 2 / 7 | |
| 1.4.4 | 2 / 9 | |
| 1.4.3 | 2 / 9 | |
| 1.4.2 | 2 / 9 | |
| 1.4.1 | 2 / 9 | |
| 1.4.0 | 2 / 9 | |
| 1.3.34 | 1 / 9 | |
| 1.3.33 | 1 / 9 | |
| 1.3.32 | 1 / 9 | |
| 1.3.31 | 1 / 9 | |
| 1.3.30 | 1 / 9 | |
| 1.3.29 | 1 / 9 | |
| 1.3.28 | 1 / 9 | |
| 1.3.27 | 2 / 1 | |
| 1.3.26 | 2 / 1 | |
| 1.3.25 | 2 / 1 | |
| 1.3.24 | 2 / 1 | |
| 1.3.23 | 0 / 1 | |
| 1.3.22 | 0 / 1 | |
| 1.3.18 | 0 / 1 |
v1.6.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.9
2 findingsPackage name '@better-auth/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.11
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.10
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.9
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.8
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.