@lark-apaas/miaoda-inspector
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Declared dependency; used indirectly via config/build tooling. | ai | |
| phantom-deps | phantom-dep:hotkeys-js | AI (phantom-deps): Declared dependency; used indirectly via config/build tooling. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Declared dependency; used indirectly via config/build tooling. | ai | |
| phantom-deps | phantom-dep:react-dev-utils | AI (phantom-deps): Declared dependency; used indirectly via config/build tooling. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.23 | 6 / 13 | |
| 1.0.22 | 6 / 13 | |
| 1.0.4 | 5 / 9 | |
| 1.0.3 | 5 / 9 | |
| 1.0.2 | 5 / 9 | |
| 1.0.1 | 5 / 9 | |
| 1.0.0 | 5 / 9 |
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.