@lytjs/devtools
Lyt.js 浏览器开发者工具 - 提供组件树检查、状态查看、性能分析和时间旅行调试
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@lytjs/vdom | AI (phantom-deps): Same-org workspace dep in a devtools umbrella; re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@lytjs/store | AI (phantom-deps): Same-org workspace dep in a devtools umbrella; re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@lytjs/router | AI (phantom-deps): Same-org workspace dep in a devtools umbrella; re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@lytjs/component | AI (phantom-deps): Same-org workspace dep in a devtools umbrella; re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@lytjs/common-dom | AI (phantom-deps): Same-org workspace dep in a devtools umbrella; re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@lytjs/common-env | AI (phantom-deps): Same-org workspace dep in a devtools umbrella; re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@lytjs/reactivity | AI (phantom-deps): Same-org workspace dep in a devtools umbrella; re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@lytjs/common-object | AI (phantom-deps): Same-org workspace dep in a devtools umbrella; re-exported rather than directly imported. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 6.9.6 | 9 / 3 | |
| 6.9.5 | 9 / 3 | |
| 6.9.4 | 9 / 3 | |
| 6.9.3 | 9 / 3 | |
| 6.9.2 | 9 / 3 | |
| 6.9.1 | 9 / 3 | |
| 6.9.0 | 9 / 3 | |
| 6.8.0 | 9 / 3 | |
| 6.7.0 | 9 / 3 | |
| 6.6.0 | 9 / 3 | |
| 6.5.0 | 9 / 3 | |
| 6.4.0 | 9 / 3 | |
| 6.0.0 | 9 / 3 | |
| 5.0.1 | 0 / 0 | |
| 4.2.0 | 0 / 0 | |
| 4.1.0 | 0 / 0 | |
| 4.0.5 | 0 / 0 | |
| 4.0.4 | 0 / 0 | |
| 4.0.1 | 0 / 0 | |
| 4.0.0 | 0 / 0 | |
| 3.2.0 | 0 / 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.
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
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
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.