@nextclaw/channel-runtime
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Scoped package with established ecosystem trust; provenance absence is acceptable. | ai | |
| phantom-deps | phantom-dep:socket.io-msgpack-parser | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:@larksuiteoapi/node-sdk | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Channel runtime with optional per-channel deps; ws loaded conditionally, not directly imported. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): Indirect/implicit runtime dep; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:imapflow | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:discord.js | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:mailparser | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:nodemailer | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:node-telegram-bot-api | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:@nextclaw/core | AI (phantom-deps): Same-org peer dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@slack/web-api | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:dingtalk-stream | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:qq-official-bot | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:@slack/socket-mode | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Optional channel adapter dep; conditionally loaded. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Young scoped package with legitimate exports and dependencies; sparse metadata is common for internal/specialized packages. | ai | |
| dependencies | unvetted-dep:dingtalk-stream | AI (dependencies): Legitimate DingTalk messaging SDK; consistent with multi-channel runtime purpose. | ai | |
| dependencies | unvetted-dep:socket.io-msgpack-parser | AI (dependencies): Standard socket.io msgpack parser; consistent with socket.io-client usage in this package. | ai | |
| dependencies | unvetted-dep:node-telegram-bot-api | AI (dependencies): Well-known Telegram bot library; consistent with multi-channel runtime purpose. | ai | |
| dependencies | unvetted-dep:qq-official-bot | AI (dependencies): Legitimate QQ official bot SDK; consistent with multi-channel runtime purpose. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.4.37 | 14 / 8 | |
| 0.4.36 | 14 / 8 | |
| 0.4.35 | 14 / 8 | |
| 0.4.29 | 14 / 8 | |
| 0.4.28 | 14 / 8 | |
| 0.4.25 | 14 / 8 | |
| 0.4.24 | 14 / 8 | |
| 0.4.22 | 14 / 8 | |
| 0.4.19 | 14 / 8 | |
| 0.4.17 | 14 / 9 | |
| 0.4.16 | 14 / 9 | |
| 0.4.14 | 14 / 9 | |
| 0.4.11 | 14 / 9 | |
| 0.4.10 | 14 / 9 | |
| 0.4.9 | 14 / 9 | |
| 0.4.8 | 14 / 9 | |
| 0.4.7 | 14 / 9 | |
| 0.4.6 | 14 / 9 | |
| 0.4.5 | 14 / 9 | |
| 0.4.4 | 14 / 9 | |
| 0.4.3 | 14 / 9 | |
| 0.4.2 | 14 / 9 | |
| 0.4.0 | 15 / 9 | |
| 0.2.12 | 15 / 9 | |
| 0.2.10 | 15 / 9 | |
| 0.2.3 | 15 / 9 | |
| 0.2.2 | 15 / 9 | |
| 0.2.1 | 15 / 9 | |
| 0.1.35 | 15 / 13 | |
| 0.1.34 | 15 / 13 | |
| 0.1.31 | 15 / 13 | |
| 0.1.28 | 15 / 13 | |
| 0.1.26 | 15 / 13 | |
| 0.1.25 | 15 / 13 | |
| 0.1.23 | 15 / 13 | |
| 0.1.22 | 15 / 13 | |
| 0.1.21 | 15 / 13 | |
| 0.1.17 | 15 / 13 | |
| 0.1.12 | 15 / 13 | |
| 0.1.10 | 15 / 13 | |
| 0.1.9 | 15 / 13 | |
| 0.1.8 | 15 / 13 | |
| 0.1.4 | 15 / 13 | |
| 0.1.3 | 15 / 13 | |
| 0.1.2 | 15 / 13 | |
| 0.1.1 | 15 / 13 |
v0.4.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.