@dbml/cli
See our website [@dbml/cli](https://dbml.dbdiagram.io/cli/) for more information
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:pegjs-require-import | AI (dependencies): pegjs-require-import is a PEG.js utility consistent with DBML's parser architecture; stable dependency across versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process import is in __tests__/cli.test.ts (test file only), not in runtime code. | ai | |
| phantom-deps | phantom-dep:@dbml/parse | AI (phantom-deps): Same org scoped package; phantom-dep heuristic unreliable for intra-monorepo deps. | ai | |
| phantom-deps | phantom-dep:@babel/cli | AI (phantom-deps): Build tooling dep loaded by convention, not direct import; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @dbml/cli from holistics org; Levenshtein match to 'joi' is purely coincidental. | ai | |
| phantom-deps | phantom-dep:bluebird | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:strip-ansi | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pegjs-require-import | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:esm | AI (phantom-deps): ESM loader referenced in config, not directly imported; stable false positive. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 8.2.5 | 13 / 0 | |
| 8.2.4 | 13 / 0 | |
| 8.2.3 | 13 / 0 | |
| 8.2.2 | 13 / 0 | |
| 8.2.1 | 13 / 0 | |
| 7.1.2 | 13 / 0 | |
| 7.1.1 | 13 / 0 | |
| 7.1.0 | 13 / 0 | |
| 7.0.0 | 12 / 0 | |
| 6.4.0 | 12 / 0 | |
| 6.3.0 | 12 / 0 | |
| 6.2.1 | 12 / 0 | |
| 6.2.0 | 12 / 0 | |
| 6.1.0 | 12 / 16 | |
| 6.0.0 | 12 / 16 | |
| 5.5.1 | 12 / 16 | |
| 5.5.0 | 12 / 16 | |
| 5.4.1 | 12 / 16 | |
| 5.3.0 | 12 / 15 | |
| 5.2.0 | 12 / 15 | |
| 5.1.0 | 12 / 7 |
v8.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (huy-dna) than the most recent previously approved version (huyleminh01) on 2026-05-26, but huy-dna is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.