← Home

@hed-hog/category

npm

```markdown # @hed-hog/category

14
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

gabrielhcodejoaohcrangel

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 14 of 117)

Version Deps Published
0.0.122 10 / 0
0.0.118 10 / 0
0.0.115 10 / 0
0.0.114 10 / 0
0.0.104 10 / 0
0.0.103 10 / 0
0.0.102 10 / 0
0.0.68 10 / 0
0.0.64 10 / 0
0.0.58 10 / 0
0.0.57 10 / 0
0.0.55 10 / 0
0.0.8 10 / 0
0.0.6 10 / 0

v0.0.122

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.118

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.115

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.114

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.104

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.103

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.102

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.68

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.64

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.58

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.57

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.55

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.