← Home

@lm_fe/pages-mchc

npm

mchc 页面级模块

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

noah1999

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@lm_fe/pages AI (dependencies): Same-org monorepo sibling; stable pattern across versions. ai
dependencies unvetted-dep:@lm_fe/provoke AI (dependencies): Same-org monorepo sibling; stable pattern across versions. ai
dependencies unvetted-dep:@lm_fe/components AI (dependencies): Same-org monorepo sibling; stable pattern across versions. ai
phantom-deps phantom-dep:@lm_fe/scripts AI (phantom-deps): @lm_fe/scripts is explicitly declared in dependencies; phantom-dep fires because it's not directly imported, stable FP for this package. ai

Versions (showing 8 of 8)

Version Deps Published
0.2.12 8 / 1
0.2.11 8 / 1
0.2.10 8 / 1
0.2.8 8 / 1
0.2.6 8 / 1
0.2.5 8 / 1
0.2.2 8 / 1
0.1.213 12 / 1

v0.2.11

1 finding
LOW No provenance attestation provenance

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

v0.2.10

1 finding
LOW No provenance attestation provenance

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

v0.2.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.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

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.2.2

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.1.213

1 finding
LOW No provenance attestation provenance

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