@liteforge/core
Signals-based reactivity core for LiteForge. Create signals, computed values, and effects with fine-grained DOM updates.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @liteforge/core is a reactivity framework, not a typosquat of cors; name similarity is coincidental. | ai |
v0.1.1
3 findingsPackage name '@liteforge/core' is 1 edit(s) away from popular package 'cors'.
Maintainer email '[email protected]' uses domain 'schildw3rk.dev' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
3 findingsPackage name '@liteforge/core' is 1 edit(s) away from popular package 'cors'.
Maintainer email '[email protected]' uses domain 'schildw3rk.dev' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.