@lytjs/component
Lyt.js 组件系统 - defineComponent、生命周期、插槽、KeepAlive、Suspense
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are @lytjs/* namespace siblings; consistent with monorepo decomposition, not third-party injection. | ai | |
| phantom-deps | phantom-dep:@lytjs/shared-types | AI (phantom-deps): Same-org types-only package; likely used only in type positions and not imported at runtime. | ai | |
| source-diff | obfuscated-file:dist/builtins-entry.cjs | AI (source-diff): File is standard minified bundler output (esbuild/rollup). Code is readable component logic with no malicious patterns — no eval, no network calls, no encoded payloads. | ai | |
| source-diff | obfuscated-file:dist/builtins-entry.mjs | AI (source-diff): File is standard minified bundler output (esbuild/rollup). Code is readable component logic with no malicious patterns — no eval, no network calls, no encoded payloads. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 6.9.6 | 8 / 3 | |
| 6.9.5 | 8 / 3 | |
| 6.9.4 | 8 / 3 | |
| 6.9.3 | 8 / 3 | |
| 6.9.2 | 8 / 3 | |
| 6.9.1 | 8 / 3 | |
| 6.9.0 | 8 / 3 | |
| 6.8.0 | 8 / 3 | |
| 6.7.0 | 8 / 3 | |
| 6.6.0 | 8 / 3 | |
| 6.5.0 | 8 / 3 | |
| 6.4.0 | 8 / 3 | |
| 6.0.0 | 8 / 3 | |
| 5.0.1 | 2 / 0 | |
| 5.0.0 | 2 / 0 | |
| 4.2.0 | 2 / 0 | |
| 4.1.0 | 2 / 0 | |
| 4.0.5 | 2 / 0 | |
| 4.0.4 | 2 / 0 | |
| 4.0.1 | 1 / 0 | |
| 4.0.0 | 1 / 0 | |
| 3.2.1 | 1 / 0 | |
| 3.1.0 | 0 / 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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: idcu.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v4.0.0
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: idcu.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.