@git.zone/cli
A comprehensive CLI tool for enhancing and managing local development workflows with gitzone utilities, focusing on project setup, version control, code formatting, and template management.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist_ts/mod_format/formatters/smartconfig.formatter.js | AI (source-diff): File contains readable compiled TS output; long lines are from inline object literals, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/mod_tools/classes.packagemanager.js | AI (source-diff): Readable TypeScript-compiled output; long lines from bundler, not obfuscation. Stable pattern for this CLI build tool. | ai | |
| source-diff | obfuscated-file:dist_ts/helpers.workflow.js | AI (source-diff): Readable TypeScript-compiled output; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/mod_release/index.js | AI (source-diff): Readable TypeScript-compiled output; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/helpers.smartconfigmigrations.js | AI (source-diff): Readable TypeScript-compiled output; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/helpers.changelog.js | AI (source-diff): Readable TypeScript-compiled output; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/mod_tools/index.js | AI (source-diff): Readable TypeScript-compiled output; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/mod_config/classes.releaseconfig.js | AI (source-diff): Compiled TypeScript output; samples show clean readable code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/mod_config/classes.commitconfig.js | AI (source-diff): Compiled TypeScript output; samples show clean readable code, not obfuscation. Long lines are likely source maps or bundler artifacts. | ai | |
| source-diff | obfuscated-file:dist_ts/mod_services/classes.globalregistry.js | AI (source-diff): Compiled TypeScript output; samples show clean readable code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/mod_config/index.js | AI (source-diff): Compiled TypeScript output; samples show clean readable code, not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 125 versions; no provenance is consistent with its history. | ai | |
| phantom-deps | phantom-dep:@push.rocks/smartchok | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/through2 | AI (phantom-deps): Type-only package; not imported at runtime, stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @git.zone/cli vs unscoped 'joi' — Levenshtein match is a false positive; no brand impersonation. | ai | |
| phantom-deps | phantom-dep:@push.rocks/smartmustache | AI (phantom-deps): Declared dep used indirectly via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@push.rocks/smartnpm | AI (phantom-deps): Declared dep used indirectly via config; stable false positive for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 28 / 4 | |
| 2.15.0 | 28 / 4 | |
| 2.14.3 | 28 / 4 | |
| 2.14.2 | 28 / 4 | |
| 2.14.1 | 28 / 4 | |
| 2.14.0 | 28 / 4 | |
| 2.13.15 | 28 / 4 | |
| 2.13.13 | 28 / 4 | |
| 2.13.12 | 28 / 4 | |
| 2.13.11 | 28 / 4 | |
| 2.13.10 | 34 / 4 | |
| 2.13.8 | 34 / 4 | |
| 2.13.7 | 30 / 8 | |
| 2.13.6 | 30 / 8 | |
| 2.13.5 | 30 / 8 | |
| 2.13.4 | 30 / 8 | |
| 2.13.3 | 30 / 8 | |
| 2.13.2 | 30 / 8 | |
| 2.13.1 | 30 / 8 | |
| 2.13.0 | 30 / 8 | |
| 2.12.2 | 30 / 8 | |
| 2.11.1 | 30 / 8 | |
| 2.11.0 | 30 / 8 | |
| 2.10.0 | 30 / 8 | |
| 2.9.2 | 30 / 8 | |
| 2.9.1 | 30 / 8 | |
| 2.9.0 | 30 / 8 | |
| 1.21.0 | 29 / 9 |
v2.18.0
8 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
6 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.13
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.12
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.11
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.