@lm_fe/components
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/a_chunks/components.src.MyImageEditor.js | AI (source-diff): Babel-transpiled React component code with standard imports; not obfuscated. | ai | |
| phantom-deps | phantom-dep:history | AI (phantom-deps): Component library pattern; referenced in config files only. | ai | |
| phantom-deps | phantom-dep:react-dnd | AI (phantom-deps): Component library pattern; referenced in config files only. | ai | |
| phantom-deps | phantom-dep:antd-img-crop | AI (phantom-deps): Component library pattern; referenced in config files only. | ai | |
| phantom-deps | phantom-dep:monaco-editor | AI (phantom-deps): Component library pattern; referenced in config files only. | ai | |
| phantom-deps | phantom-dep:@lm_fe/scripts | AI (phantom-deps): Same org scope; used as build/tooling dep, stable false positive. | ai | |
| phantom-deps | phantom-dep:quill | AI (phantom-deps): Component library pattern; quill referenced in config/optional components, not a direct import. | ai | |
| phantom-deps | phantom-dep:react-resizable | AI (phantom-deps): Component library pattern; referenced in config files only. | ai | |
| phantom-deps | phantom-dep:@monaco-editor/react | AI (phantom-deps): Component library pattern; referenced in config files only. | ai | |
| phantom-deps | phantom-dep:react-dnd-html5-backend | AI (phantom-deps): Component library pattern; referenced in config files only. | ai | |
| phantom-deps | phantom-dep:quill-image-resize-module | AI (phantom-deps): Component library pattern; referenced in config files only. | ai | |
| phantom-deps | phantom-dep:react-to-print | AI (phantom-deps): Component library pattern; referenced in config files only. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.12 | 6 / 7 | |
| 0.2.11 | 6 / 7 | |
| 0.2.10 | 6 / 7 | |
| 0.2.8 | 6 / 7 | |
| 0.2.7 | 6 / 7 | |
| 0.2.6 | 6 / 7 | |
| 0.2.5 | 6 / 7 | |
| 0.2.2 | 6 / 7 | |
| 0.1.211 | 21 / 4 | |
| 0.1.206 | 21 / 4 | |
| 0.1.205 | 21 / 4 | |
| 0.1.201 | 21 / 7 |
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.211
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.206
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.205
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.