@lark-apaas/openclaw-extension-miaoda
妙搭 OpenClaw 插件
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package under @lark-apaas org; missing metadata is typical for private/enterprise packages, not spam. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api-logs | AI (phantom-deps): Bundled via tsdown; not directly imported in source but legitimately used. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-logs | AI (phantom-deps): Bundled via tsdown; not directly imported in source but legitimately used. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): Bundled via tsdown; not directly imported in source but legitimately used. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api | AI (phantom-deps): Bundled via tsdown; not directly imported in source but legitimately used. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/semantic-conventions | AI (phantom-deps): Bundled via tsdown; not directly imported in source but legitimately used. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-logs-otlp-http | AI (phantom-deps): Bundled via tsdown; not directly imported in source but legitimately used. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-metrics-otlp-http | AI (phantom-deps): Bundled via tsdown; not directly imported in source but legitimately used. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-metrics | AI (phantom-deps): Bundled via tsdown; not directly imported in source but legitimately used. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.0.21 | 9 / 6 | |
| 1.0.20 | 9 / 6 | |
| 1.0.19 | 9 / 6 | |
| 1.0.18 | 9 / 6 | |
| 1.0.17 | 9 / 6 | |
| 1.0.16 | 8 / 6 | |
| 1.0.15 | 8 / 6 | |
| 1.0.14 | 8 / 6 | |
| 1.0.13 | 8 / 5 | |
| 1.0.12 | 8 / 5 | |
| 1.0.11 | 8 / 5 | |
| 1.0.10 | 0 / 5 | |
| 1.0.9 | 0 / 5 | |
| 1.0.8 | 0 / 5 | |
| 1.0.7 | 0 / 5 | |
| 1.0.6 | 0 / 5 | |
| 1.0.5 | 0 / 5 | |
| 1.0.4 | 0 / 5 | |
| 1.0.3 | 0 / 5 | |
| 1.0.2 | 0 / 5 | |
| 1.0.1 | 0 / 5 |
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.