@linked-db/linked-ql
The application-flavoured SQL that runs anywhere, with pluggable, composable backends, with an offline- and sync-ready model
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Declared dependency; used for config parsing in this package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Declared dependency; used for environment variable loading. | ai | |
| phantom-deps | phantom-dep:enquirer | AI (phantom-deps): Declared dependency; used for CLI prompts in this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.1.10 | 9 / 14 | |
| 1.1.9 | 9 / 14 | |
| 1.1.8 | 9 / 14 | |
| 1.1.7 | 9 / 14 | |
| 1.1.6 | 9 / 14 | |
| 1.1.5 | 9 / 14 | |
| 1.1.4 | 9 / 14 | |
| 1.1.3 | 9 / 14 | |
| 1.1.2 | 9 / 14 | |
| 1.1.1 | 9 / 14 | |
| 1.1.0 | 9 / 14 |
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
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.