@duckcodeailabs/dql-core
DQL language core: lexer, parser, AST, semantic analysis
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Consistent with normal feature growth in an actively developed language-tooling package. | ai | |
| provenance | missing-githead | AI (provenance): No malicious behavior tied to it; publisher has long clean track record. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Frequent releases are normal for this fast-moving package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): node-sql-parser is a well-established SQL parsing library; its addition is consistent with dql-core's stated purpose as a query language parser. Not a suspicious dependency. | ai | |
| provenance | no-provenance | AI (provenance): Package has a legitimate repo and ecosystem presence; lack of Sigstore provenance is a process gap, not a security indicator for this package. | ai | |
| dependencies | unvetted-dep:node-sql-parser | AI (dependencies): node-sql-parser is a well-established SQL parsing library; its use in a query language core package is expected and appropriate. | ai | |
| phantom-deps | phantom-dep:node-sql-parser | AI (phantom-deps): node-sql-parser is declared as a runtime dependency and its indirect/config-level usage is consistent with a TypeScript query language library. | ai |
Versions (showing 29 of 129)
| Version | Deps | Published |
|---|---|---|
| 0.8.16 | 1 / 4 | |
| 0.8.15 | 1 / 4 | |
| 0.8.14 | 1 / 4 | |
| 0.8.13 | 1 / 4 | |
| 0.8.12 | 1 / 4 | |
| 0.8.11 | 1 / 4 | |
| 0.8.10 | 1 / 4 | |
| 0.8.9 | 1 / 4 | |
| 0.8.8 | 1 / 4 | |
| 0.8.7 | 1 / 4 | |
| 0.8.6 | 1 / 4 | |
| 0.8.5 | 1 / 4 | |
| 0.8.4 | 1 / 4 | |
| 0.8.3 | 1 / 4 | |
| 0.8.2 | 1 / 4 | |
| 0.8.1 | 1 / 4 | |
| 0.8.0 | 1 / 4 | |
| 0.7.1 | 1 / 4 | |
| 0.7.0 | 1 / 4 | |
| 0.6.0 | 1 / 4 | |
| 0.3.2 | 1 / 4 | |
| 0.3.1 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.0 | 1 / 4 | |
| 0.1.4 | 0 / 3 | |
| 0.1.3 | 0 / 3 | |
| 0.1.2 | 0 / 3 | |
| 0.1.1 | 0 / 3 | |
| 0.1.0 | 0 / 3 |
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.