@sqldoc/cli
CLI tool for sqldoc -- compile and validate SQL files with tag-driven generation
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): env-spread in auto-install.ts is passing environment to a child process installer — standard pattern, not exfiltration. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @sqldoc/cli is a SQL doc CLI tool; Levenshtein match to 'joi' is coincidental. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.2.9 | 5 / 2 | |
| 0.2.8 | 5 / 2 | |
| 0.2.7 | 5 / 2 | |
| 0.2.6 | 5 / 2 | |
| 0.2.5 | 5 / 2 | |
| 0.2.4 | 5 / 2 | |
| 0.2.3 | 5 / 2 | |
| 0.2.2 | 5 / 2 | |
| 0.2.1 | 5 / 2 | |
| 0.2.0 | 5 / 2 | |
| 0.1.3 | 5 / 2 | |
| 0.1.2 | 5 / 2 | |
| 0.1.1 | 5 / 2 | |
| 0.1.0 | 5 / 2 | |
| 0.0.10 | 5 / 2 | |
| 0.0.9 | 4 / 2 | |
| 0.0.8 | 5 / 2 | |
| 0.0.7 | 5 / 2 | |
| 0.0.6 | 5 / 2 | |
| 0.0.5 | 5 / 2 | |
| 0.0.4 | 5 / 2 | |
| 0.0.3 | 5 / 2 | |
| 0.0.2 | 5 / 2 |
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
2 findingsSpreading entire process.env into an object — may capture all secrets 64 | 65 | let installArgs: string[] > 66 | const env: Record<string, string> = { ...process.env } as Record<string, string> 67 | 68 | if (isBunBinary) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
2 findingsSpreading entire process.env into an object — may capture all secrets 64 | 65 | let installArgs: string[] > 66 | const env: Record<string, string> = { ...process.env } as Record<string, string> 67 | 68 | if (isBunBinary) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
2 findingsSpreading entire process.env into an object — may capture all secrets 64 | 65 | let installArgs: string[] > 66 | const env: Record<string, string> = { ...process.env } as Record<string, string> 67 | 68 | if (isBunBinary) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
2 findingsSpreading entire process.env into an object — may capture all secrets 64 | 65 | let installArgs: string[] > 66 | const env: Record<string, string> = { ...process.env } as Record<string, string> 67 | 68 | if (isBunBinary) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
2 findingsSpreading entire process.env into an object — may capture all secrets 64 | 65 | let installArgs: string[] > 66 | const env: Record<string, string> = { ...process.env } as Record<string, string> 67 | 68 | if (isBunBinary) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
2 findingsSpreading entire process.env into an object — may capture all secrets 64 | 65 | let installArgs: string[] > 66 | const env: Record<string, string> = { ...process.env } as Record<string, string> 67 | 68 | if (isBunBinary) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
2 findingsSpreading entire process.env into an object — may capture all secrets 64 | 65 | let installArgs: string[] > 66 | const env: Record<string, string> = { ...process.env } as Record<string, string> 67 | 68 | if (isBunBinary) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
2 findingsSpreading entire process.env into an object — may capture all secrets 64 | 65 | let installArgs: string[] > 66 | const env: Record<string, string> = { ...process.env } as Record<string, string> 67 | 68 | if (isBunBinary) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
2 findingsSpreading entire process.env into an object — may capture all secrets 64 | 65 | let installArgs: string[] > 66 | const env: Record<string, string> = { ...process.env } as Record<string, string> 67 | 68 | if (isBunBinary) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.