@hed-hog/cli
HedHog CLI tool
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Young CLI tool; lack of provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a standard NestJS peer dependency used implicitly by the framework. | ai | |
| phantom-deps | phantom-dep:@nestjs/core | AI (phantom-deps): NestJS core is used implicitly via nest-commander and framework bootstrapping. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): Known implicit NestJS runtime dependency for decorators. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped NestJS CLI package; name similarity to 'joi' is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:boxen | AI (phantom-deps): CLI display library; likely used in compiled output referenced by config. | ai | |
| phantom-deps | phantom-dep:cli-table3 | AI (phantom-deps): CLI table library; likely used in compiled output referenced by config. | ai | |
| phantom-deps | phantom-dep:@nestjs/platform-express | AI (phantom-deps): Standard NestJS platform adapter, used implicitly by the framework. | ai |
Versions (showing 51 of 71)
| Version | Deps | Published |
|---|---|---|
| 0.0.97 | 17 / 28 | |
| 0.0.96 | 17 / 28 | |
| 0.0.95 | 17 / 28 | |
| 0.0.94 | 17 / 28 | |
| 0.0.93 | 17 / 28 | |
| 0.0.92 | 17 / 28 | |
| 0.0.91 | 17 / 28 | |
| 0.0.90 | 17 / 28 | |
| 0.0.88 | 17 / 28 | |
| 0.0.87 | 17 / 28 | |
| 0.0.86 | 17 / 28 | |
| 0.0.85 | 17 / 28 | |
| 0.0.84 | 17 / 28 | |
| 0.0.81 | 17 / 28 | |
| 0.0.80 | 17 / 28 | |
| 0.0.79 | 17 / 28 | |
| 0.0.78 | 17 / 28 | |
| 0.0.76 | 17 / 28 | |
| 0.0.75 | 17 / 28 | |
| 0.0.74 | 17 / 28 | |
| 0.0.73 | 17 / 28 | |
| 0.0.72 | 17 / 28 | |
| 0.0.71 | 17 / 28 | |
| 0.0.70 | 17 / 28 | |
| 0.0.69 | 17 / 28 | |
| 0.0.68 | 17 / 28 | |
| 0.0.67 | 17 / 28 | |
| 0.0.66 | 17 / 28 | |
| 0.0.65 | 17 / 28 | |
| 0.0.64 | 17 / 28 | |
| 0.0.63 | 17 / 28 | |
| 0.0.62 | 17 / 28 | |
| 0.0.61 | 17 / 28 | |
| 0.0.60 | 17 / 28 | |
| 0.0.59 | 17 / 28 | |
| 0.0.55 | 17 / 28 | |
| 0.0.54 | 17 / 28 | |
| 0.0.53 | 17 / 28 | |
| 0.0.52 | 17 / 28 | |
| 0.0.51 | 17 / 28 | |
| 0.0.50 | 17 / 28 | |
| 0.0.49 | 17 / 28 | |
| 0.0.48 | 17 / 28 | |
| 0.0.47 | 17 / 28 | |
| 0.0.46 | 17 / 28 | |
| 0.0.45 | 17 / 28 | |
| 0.0.44 | 17 / 28 | |
| 0.0.43 | 17 / 28 | |
| 0.0.42 | 17 / 28 | |
| 0.0.41 | 17 / 28 | |
| 0.0.40 | 17 / 28 |
v0.0.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.