@freehour/supabase-core
Lightweight services for supabase to make it easier to work with databases, tables and storage buckets
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Low-severity, common across npm; no other risk signals present for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall copies bundled Supabase migration assets; script is included in package files and is not network-fetching. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 2 / 11 | |
| 2.1.1 | 2 / 11 | |
| 2.1.0 | 4 / 9 | |
| 2.0.4 | 5 / 8 | |
| 2.0.1 | 5 / 8 | |
| 2.0.0 | 5 / 8 | |
| 1.7.2 | 5 / 8 | |
| 1.7.0 | 5 / 8 | |
| 1.6.0 | 6 / 8 | |
| 1.5.4 | 6 / 8 | |
| 1.5.3 | 6 / 16 | |
| 1.5.1 | 6 / 16 | |
| 1.5.0 | 6 / 16 | |
| 1.4.0 | 6 / 16 | |
| 1.1.2 | 5 / 16 | |
| 1.1.0 | 5 / 16 | |
| 1.0.1 | 4 / 16 | |
| 1.0.0 | 4 / 16 |
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsScript: bun ./scripts/copy-supabase-assets.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
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.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.