← Home

@lm_fe/pages

npm
15
Versions
—
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
source-diff obfuscated-file:dist/a_chunks/src.pages.questionnaire.js AI (source-diff): Rollup bundle output with long CSS lines; not obfuscation. Stable for this package. ai
phantom-deps phantom-dep:history AI (phantom-deps): Config-referenced dependency; stable pattern for internal monorepo packages. ai
phantom-deps phantom-dep:braft-editor AI (phantom-deps): Config-referenced dependency; stable pattern for internal monorepo packages. ai
phantom-deps phantom-dep:qrcode.react AI (phantom-deps): Config-referenced dependency; stable pattern for internal monorepo packages. ai
bogus-package bogus-package AI (bogus-package): Internal monorepo package; missing metadata (repo, description, keywords) is expected and not indicative of malice. ai
phantom-deps phantom-dep:@lm_fe/scripts AI (phantom-deps): Same-org scoped package; declared as runtime dep in package.json, phantom detection is a false positive here. ai

Versions (showing 15 of 15)

Version Deps Published
0.2.12 8 / 3
0.2.11 8 / 3
0.2.10 8 / 3
0.2.8 8 / 3
0.2.7 8 / 3
0.2.6 8 / 3
0.2.5 8 / 3
0.2.2 8 / 3
0.1.211 13 / 1
0.1.210 13 / 1
0.1.209 13 / 1
0.1.207 13 / 1
0.1.206 13 / 1
0.1.205 13 / 1
0.1.201 13 / 1

v0.2.11

2 findings
HIGH New obfuscated file: dist/a_chunks/src.pages.questionnaire.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.2.8

2 findings
HIGH New obfuscated file: dist/a_chunks/src.pages.questionnaire.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.2.7

2 findings
HIGH New obfuscated file: dist/a_chunks/src.pages.questionnaire.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.2.6

2 findings
HIGH New obfuscated file: dist/a_chunks/src.pages.questionnaire.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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

1 finding
LOW No provenance attestation provenance

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

v0.1.210

1 finding
LOW No provenance attestation provenance

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

v0.1.209

1 finding
LOW No provenance attestation provenance

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

v0.1.207

1 finding
LOW No provenance attestation provenance

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

v0.1.206

1 finding
LOW No provenance attestation provenance

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

v0.1.205

1 finding
LOW No provenance attestation provenance

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

v0.1.201

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.