@hed-hog/category
```markdown # @hed-hog/category
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@nestjs/jwt | AI (phantom-deps): NestJS config-referenced dependency; stable pattern in this monorepo. | ai | |
| phantom-deps | phantom-dep:@nestjs/core | AI (phantom-deps): NestJS config-referenced dependency; stable pattern in this monorepo. | ai | |
| phantom-deps | phantom-dep:@nestjs/config | AI (phantom-deps): NestJS config-referenced dependency; stable pattern in this monorepo. | ai | |
| phantom-deps | phantom-dep:@nestjs/mapped-types | AI (phantom-deps): NestJS config-referenced dependency; stable pattern in this monorepo. | ai | |
| phantom-deps | phantom-dep:@hed-hog/core | AI (phantom-deps): Same-org scoped dependency; stable pattern in this monorepo. | ai |
Versions (showing 51 of 114)
| Version | Deps | Published |
|---|---|---|
| 0.0.362 | 10 / 0 | |
| 0.0.361 | 10 / 0 | |
| 0.0.358 | 10 / 0 | |
| 0.0.356 | 10 / 0 | |
| 0.0.355 | 10 / 0 | |
| 0.0.354 | 10 / 0 | |
| 0.0.353 | 10 / 0 | |
| 0.0.351 | 10 / 0 | |
| 0.0.350 | 10 / 0 | |
| 0.0.349 | 10 / 0 | |
| 0.0.347 | 10 / 0 | |
| 0.0.338 | 10 / 0 | |
| 0.0.333 | 10 / 0 | |
| 0.0.332 | 10 / 0 | |
| 0.0.331 | 10 / 0 | |
| 0.0.330 | 10 / 0 | |
| 0.0.329 | 10 / 0 | |
| 0.0.328 | 10 / 0 | |
| 0.0.327 | 10 / 0 | |
| 0.0.326 | 10 / 0 | |
| 0.0.325 | 10 / 0 | |
| 0.0.322 | 10 / 0 | |
| 0.0.321 | 10 / 0 | |
| 0.0.319 | 10 / 0 | |
| 0.0.318 | 10 / 0 | |
| 0.0.317 | 10 / 0 | |
| 0.0.316 | 10 / 0 | |
| 0.0.315 | 10 / 0 | |
| 0.0.314 | 10 / 0 | |
| 0.0.312 | 10 / 0 | |
| 0.0.311 | 10 / 0 | |
| 0.0.310 | 10 / 0 | |
| 0.0.309 | 10 / 0 | |
| 0.0.306 | 10 / 0 | |
| 0.0.305 | 10 / 0 | |
| 0.0.304 | 10 / 0 | |
| 0.0.303 | 10 / 0 | |
| 0.0.302 | 10 / 0 | |
| 0.0.301 | 10 / 0 | |
| 0.0.300 | 10 / 0 | |
| 0.0.299 | 10 / 0 | |
| 0.0.298 | 10 / 0 | |
| 0.0.297 | 10 / 0 | |
| 0.0.296 | 10 / 0 | |
| 0.0.295 | 10 / 0 | |
| 0.0.294 | 10 / 0 | |
| 0.0.293 | 10 / 0 | |
| 0.0.292 | 10 / 0 | |
| 0.0.291 | 10 / 0 | |
| 0.0.286 | 10 / 0 | |
| 0.0.285 | 10 / 0 |
v0.0.362
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.361
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.358
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.356
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.355
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.354
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.353
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.351
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.350
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.349
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.347
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.338
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.333
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.332
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.331
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.330
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.329
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.328
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.327
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.326
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.325
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.322
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.321
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.319
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.318
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.317
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.316
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.315
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.314
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.312
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.311
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.310
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.309
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.305
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.304
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.303
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.302
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.301
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.300
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.299
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.298
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.297
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.296
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.295
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.294
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.293
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.292
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.291
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.286
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.285
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.