@lytjs/core
Lyt.js 核心入口 - 整合响应式、编译器、虚拟 DOM、渲染器和组件系统
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase is accounted for by two large source map files added in this version, not injected payload. | ai | |
| phantom-deps | phantom-dep:@lytjs/shared-types | AI (phantom-deps): Same-org monorepo type-only dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lytjs/common-string | AI (phantom-deps): Same-org monorepo workspace dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @lytjs/core is the core module of the Lyt.js framework, not a typosquat of cors. The scoped namespace, framework context, and sibling packages make confusion implausible. | ai | |
| phantom-deps | phantom-dep:@lytjs/vdom | AI (phantom-deps): @lytjs/vdom is a same-org workspace sibling; it is bundled into dist and may not appear as a direct import in source analysis. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 6.9.6 | 11 / 4 | |
| 6.9.5 | 11 / 4 | |
| 6.9.4 | 11 / 4 | |
| 6.9.3 | 11 / 4 | |
| 6.9.2 | 11 / 4 | |
| 6.9.1 | 11 / 4 | |
| 6.9.0 | 11 / 4 | |
| 6.8.0 | 11 / 4 | |
| 6.7.0 | 11 / 4 | |
| 6.6.0 | 11 / 4 | |
| 6.5.0 | 11 / 4 | |
| 6.4.0 | 11 / 4 | |
| 6.0.0 | 11 / 4 | |
| 5.0.1 | 6 / 0 | |
| 5.0.0 | 6 / 0 | |
| 4.2.0 | 6 / 0 | |
| 4.1.0 | 6 / 0 | |
| 4.0.5 | 6 / 0 | |
| 4.0.4 | 6 / 0 | |
| 4.0.1 | 5 / 0 | |
| 4.0.0 | 5 / 0 | |
| 3.2.1 | 5 / 0 | |
| 3.1.0 | 5 / 0 |
v6.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
2 findingsPackage name '@lytjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
2 findingsPackage name '@lytjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
2 findingsPackage name '@lytjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
2 findingsPackage name '@lytjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
2 findingsPackage name '@lytjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.