@lytjs/common
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@lytjs/common-string | AI (dependencies): workspace:* sibling in the same @lytjs monorepo; not a third-party dependency. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are workspace:* siblings in the @lytjs monorepo; aggregate barrel package pattern. | ai | |
| phantom-deps | phantom-dep:@lytjs/common-warn | AI (phantom-deps): Same-org workspace sibling; phantom-dep heuristic unreliable for monorepo re-exports. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 6.9.6 | 28 / 3 | |
| 6.9.5 | 28 / 3 | |
| 6.9.4 | 28 / 3 | |
| 6.9.3 | 28 / 3 | |
| 6.9.2 | 28 / 3 | |
| 6.9.1 | 28 / 3 | |
| 6.9.0 | 28 / 3 | |
| 6.8.0 | 28 / 3 | |
| 6.7.0 | 28 / 3 | |
| 6.6.0 | 28 / 3 | |
| 6.5.0 | 28 / 3 | |
| 6.4.0 | 28 / 3 | |
| 6.0.0 | 22 / 3 | |
| 5.0.1 | 0 / 0 | |
| 5.0.0 | 0 / 0 | |
| 4.2.0 | 0 / 0 | |
| 4.1.0 | 0 / 0 | |
| 4.0.5 | 0 / 0 | |
| 4.0.4 | 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.