@nextclaw/openclaw-compat
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:@nextclaw/channel-plugin-qq | AI (phantom-deps): Compat aggregator declares same-org deps without direct imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-plugin-email | AI (phantom-deps): Same-org aggregator pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-plugin-slack | AI (phantom-deps): Same-org aggregator pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-plugin-feishu | AI (phantom-deps): Same-org aggregator pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-plugin-mochat | AI (phantom-deps): Same-org aggregator pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-plugin-discord | AI (phantom-deps): Same-org aggregator pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-plugin-dingtalk | AI (phantom-deps): Same-org aggregator pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-plugin-telegram | AI (phantom-deps): Same-org aggregator pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-plugin-whatsapp | AI (phantom-deps): Same-org aggregator pattern; not a real phantom dep. | ai |
Versions (showing 22 of 122)
| Version | Deps | Published |
|---|---|---|
| 0.1.23 | 16 / 10 | |
| 0.1.21 | 16 / 10 | |
| 0.1.20 | 16 / 10 | |
| 0.1.19 | 16 / 10 | |
| 0.1.18 | 16 / 10 | |
| 0.1.17 | 16 / 10 | |
| 0.1.16 | 16 / 10 | |
| 0.1.15 | 16 / 10 | |
| 0.1.14 | 16 / 10 | |
| 0.1.13 | 15 / 10 | |
| 0.1.12 | 15 / 10 | |
| 0.1.11 | 15 / 10 | |
| 0.1.10 | 15 / 10 | |
| 0.1.9 | 15 / 10 | |
| 0.1.8 | 14 / 10 | |
| 0.1.7 | 5 / 10 | |
| 0.1.6 | 5 / 10 | |
| 0.1.5 | 5 / 10 | |
| 0.1.4 | 5 / 10 | |
| 0.1.3 | 5 / 10 | |
| 0.1.2 | 5 / 10 | |
| 0.1.1 | 5 / 10 |
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.