@lytjs/renderer
Lyt.js 渲染器 - 多平台渲染抽象层(DOM/SSR/Native/MiniApp)
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@lytjs/adapter-web | AI (dependencies): Same-org monorepo sibling; not a third-party supply chain risk. | ai | |
| dependencies | unvetted-dep:@lytjs/common-string | AI (dependencies): Same-org monorepo sibling; not a third-party supply chain risk. | ai | |
| phantom-deps | phantom-dep:@lytjs/common-dom | AI (phantom-deps): Same-org scope; likely re-exported transitively rather than directly imported. | ai | |
| source-diff | obfuscated-file:dist/ssr.cjs | AI (source-diff): Standard minified build output for SSR renderer target; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/vapor.cjs | AI (source-diff): Standard minified build output for vapor renderer target; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/dom.mjs | AI (source-diff): Standard minified ESM build output for DOM renderer; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/dom.cjs | AI (source-diff): Standard esbuild/rollup minified output for a renderer package; long lines are minification artifacts, not obfuscation. No malicious patterns in code. | ai | |
| source-diff | obfuscated-file:dist/native.mjs | AI (source-diff): Standard minified ESM build output for native renderer; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/ssr.mjs | AI (source-diff): Standard minified ESM build output for SSR renderer; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/vapor.mjs | AI (source-diff): Standard minified ESM build output for vapor renderer; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/miniapp.mjs | AI (source-diff): Standard minified ESM build output for miniapp renderer; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/miniapp.cjs | AI (source-diff): Standard minified build output for miniapp renderer target; semantically transparent virtual DOM code. | ai | |
| source-diff | obfuscated-file:dist/native.cjs | AI (source-diff): Standard minified build output for native renderer target; no malicious patterns. | 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 | 3 / 0 | |
| 5.0.0 | 3 / 0 | |
| 4.2.0 | 2 / 0 | |
| 4.1.0 | 2 / 0 | |
| 4.0.5 | 2 / 0 | |
| 4.0.4 | 2 / 0 | |
| 4.0.1 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.2.1 | 2 / 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
12 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.
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.
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.
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.
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
11 findingsNewly 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.
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.
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.
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.
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.