@hed-hog/lms
```markdown # @hed-hog/lms
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:@hed-hog/crm | AI (phantom-deps): Same org scope; declared for transitive wiring, consistent with other @hed-hog phantom deps already accepted. | ai | |
| phantom-deps | phantom-dep:@nestjs/jwt | AI (phantom-deps): NestJS peer dependency; commonly declared but not directly imported in NestJS module libraries. | ai | |
| phantom-deps | phantom-dep:@nestjs/core | AI (phantom-deps): NestJS peer dependency; commonly declared but not directly imported in NestJS module libraries. | ai | |
| phantom-deps | phantom-dep:@hed-hog/contact | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for re-exported modules. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @hed-hog/lms; levenshtein match to 'qs' is a false positive with no plausible impersonation intent. | ai | |
| phantom-deps | phantom-dep:@hed-hog/category | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for re-exported modules. | ai | |
| phantom-deps | phantom-dep:@hed-hog/api-types | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for re-exported modules. | ai | |
| phantom-deps | phantom-dep:@hed-hog/finance | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for re-exported modules. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.357 | 15 / 0 | |
| 0.0.351 | 15 / 0 | |
| 0.0.329 | 14 / 0 | |
| 0.0.322 | 14 / 0 | |
| 0.0.314 | 14 / 0 | |
| 0.0.311 | 14 / 0 | |
| 0.0.306 | 14 / 0 |
v0.0.357
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.329
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.314
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.311
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.