@lm_fe/utils
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped org package; sparse metadata is expected for monorepo utilities, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal utility package; missing description is consistent across versions and not a risk signal. | ai | |
| dependencies | unvetted-dep:store | AI (dependencies): [email protected] is a well-known localStorage abstraction library; no security concerns. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is typical for this org's packages; not a security signal on its own. | ai | |
| phantom-deps | phantom-dep:@lm_fe/static | AI (phantom-deps): Same-org sibling package declared as runtime dep; phantom-dep heuristic fires because it's not directly imported in analyzed code. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.12 | 7 / 1 | |
| 0.2.7 | 7 / 1 | |
| 0.1.211 | 6 / 2 | |
| 0.1.210 | 6 / 2 | |
| 0.1.209 | 6 / 2 | |
| 0.1.201 | 6 / 2 |
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.201
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.