@alilc/lowcode-designer
1
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
hujiulongclarencepalvartoakirakaixingmoluleoyuanleoyuan88liujuping123hzd822mark-cketernalskyjun.liyang1996sun2amazyy7259otakuxvjack.lianjiewoshilaogeqingniaotonghuawhatever_lll1ncountersoberz
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used only to validate CSS property name quoting; input is a property name string, not arbitrary user data. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Standard Proxy get-trap pattern using Reflect.get; not obfuscation. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo package; sparse README is typical for internal component packages. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 8 / 14 |
v1.3.4
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.