@launchql/core
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:@launchql/explorer | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): rimraf used in build scripts, not runtime imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@pgsql/types | AI (phantom-deps): Listed as peerDependency and used via type references; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@launchql/server-utils | AI (phantom-deps): Same-org scoped dep; likely used indirectly or via re-exports; stable false positive. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Database migration CLI tool legitimately uses child_process; stable pattern for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require used to load extension package.json by path; expected pattern for a plugin/extension loader. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @launchql/core from established publisher; not a typosquat of cors. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.18.3 | 16 / 3 | |
| 2.18.2 | 16 / 3 | |
| 2.18.1 | 16 / 3 | |
| 2.18.0 | 16 / 3 | |
| 2.17.8 | 16 / 3 | |
| 2.17.0 | 17 / 3 | |
| 2.15.0 | 18 / 3 | |
| 2.12.4 | 18 / 3 | |
| 2.11.6 | 15 / 2 | |
| 2.11.1 | 15 / 2 | |
| 2.10.0 | 15 / 2 | |
| 2.8.0 | 15 / 2 | |
| 2.1.17 | 10 / 2 |
v2.18.3
2 findingsPackage name '@launchql/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
2 findingsPackage name '@launchql/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
2 findingsPackage name '@launchql/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.4
2 findingsPackage name '@launchql/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.6
2 findingsPackage name '@launchql/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.1
2 findingsPackage name '@launchql/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
2 findingsPackage name '@launchql/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
2 findingsPackage name '@launchql/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.17
2 findingsPackage name '@launchql/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.