@duckcodeailabs/dql-slack
DQL Slack front-end: slash-command bot that answers via the block-first agent loop
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
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 3 / 3 | |
| 1.5.3 | 3 / 3 | |
| 1.5.2 | 3 / 3 | |
| 1.5.1 | 3 / 3 | |
| 1.5.0 | 3 / 3 | |
| 1.4.4 | 3 / 3 | |
| 1.4.3 | 3 / 3 | |
| 1.4.1 | 3 / 3 | |
| 1.4.0 | 3 / 3 |
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage 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.