@lark-apaas/devtool-kits
FullStack Devtool Kits
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Used via config, not direct import; common pattern. | ai | |
| phantom-deps | phantom-dep:ts-morph | AI (phantom-deps): Used via config, not direct import; common pattern. | ai | |
| phantom-deps | phantom-dep:inflection | AI (phantom-deps): Used via config, not direct import; common pattern. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.2.24 | 7 / 6 | |
| 1.2.23 | 7 / 6 | |
| 1.2.22 | 7 / 6 | |
| 1.2.21 | 7 / 6 | |
| 1.2.20 | 7 / 6 | |
| 1.2.19 | 4 / 6 | |
| 1.2.18 | 4 / 6 | |
| 1.2.17 | 4 / 6 | |
| 1.2.16 | 4 / 6 | |
| 1.2.15 | 4 / 6 | |
| 1.2.8 | 4 / 6 | |
| 1.2.7 | 4 / 6 | |
| 1.2.6 | 4 / 6 | |
| 1.2.5 | 4 / 6 | |
| 1.2.4 | 4 / 6 | |
| 1.2.3 | 4 / 6 | |
| 1.2.2 | 3 / 6 | |
| 1.2.1 | 3 / 6 | |
| 1.2.0 | 3 / 6 | |
| 1.1.0 | 2 / 6 | |
| 1.0.11 | 2 / 6 | |
| 1.0.10 | 2 / 6 | |
| 1.0.9 | 2 / 6 |
v1.2.8
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xiaochuanzhang_byted) than the most recent previously approved version (duanlikang_byte) on 2025-12-09, but xiaochuanzhang_byted is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.