@lm_fe/service
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal scoped package; provenance absence is consistent across the @lm_fe suite and not a risk signal here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.2.12 | 5 / 1 | |
| 0.2.11 | 5 / 1 | |
| 0.2.10 | 5 / 1 | |
| 0.2.8 | 5 / 1 | |
| 0.2.7 | 5 / 1 | |
| 0.2.6 | 5 / 1 | |
| 0.2.5 | 5 / 1 | |
| 0.2.2 | 5 / 1 | |
| 0.1.211 | 3 / 1 | |
| 0.1.210 | 3 / 1 | |
| 0.1.209 | 3 / 1 | |
| 0.1.207 | 3 / 1 | |
| 0.1.206 | 3 / 1 | |
| 0.1.205 | 3 / 1 | |
| 0.1.201 | 3 / 1 |
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
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.211
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.210
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.209
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.207
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.206
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.205
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.