@sportsdigita/ddcomponents-cli
A CLI for creating and publishing Digideck component repositories.
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): CLI spawns child processes needing full env; spreading process.env is intentional and standard for this use case. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool legitimately uses child_process to spawn local dev servers; expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:chai | AI (phantom-deps): Test framework dependency referenced in config files; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:mocha | AI (phantom-deps): Test framework dependency referenced in config files; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Utility library referenced in config/scripts; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): Build/cleanup tool referenced in config; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:zip-a-folder | AI (phantom-deps): Packaging utility referenced in config; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jsdevtools/chai-exec | AI (phantom-deps): Test utility referenced in config; stable false positive for this CLI package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.0.33 | 21 / 5 | |
| 1.0.32 | 21 / 5 | |
| 1.0.31 | 21 / 5 | |
| 1.0.30 | 21 / 5 | |
| 1.0.29 | 21 / 5 | |
| 1.0.28 | 21 / 5 | |
| 1.0.27 | 21 / 5 | |
| 1.0.26 | 21 / 5 | |
| 1.0.25 | 19 / 5 | |
| 1.0.24 | 19 / 5 | |
| 1.0.23 | 19 / 5 | |
| 1.0.22 | 19 / 5 |
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.