@nextclaw/service
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@nextclaw/channel-extension-telegram | AI (dependencies): Same-org package matching the pattern of all other channel-extension-* deps; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-telegram | AI (phantom-deps): Declared as builtinExtension plugin, loaded dynamically; not a static import by design. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-email | AI (phantom-deps): Declared as builtinExtension plugin, loaded dynamically; not a static import by design. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-slack | AI (phantom-deps): Declared as builtinExtension plugin, loaded dynamically; not a static import by design. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-wecom | AI (phantom-deps): Declared as builtinExtension plugin, loaded dynamically; not a static import by design. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-discord | AI (phantom-deps): Declared as builtinExtension plugin, loaded dynamically; not a static import by design. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-dingtalk | AI (phantom-deps): Declared as builtinExtension plugin, loaded dynamically; not a static import by design. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-whatsapp | AI (phantom-deps): Declared as builtinExtension plugin, loaded dynamically; not a static import by design. | ai | |
| phantom-deps | phantom-dep:@nextclaw/ncp | AI (phantom-deps): Same-org package, likely dynamically loaded; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-qq | AI (phantom-deps): Declared as builtinExtension plugin, loaded dynamically; not a static import by design. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI dep referenced in config; common phantom-dep false positive. | ai | |
| phantom-deps | phantom-dep:@nextclaw/ncp-mcp | AI (phantom-deps): Same-org dep likely dynamically loaded; stable FP. | ai | |
| phantom-deps | phantom-dep:@nextclaw/ncp-toolkit | AI (phantom-deps): Same-org dep likely dynamically loaded; stable FP. | ai | |
| phantom-deps | phantom-dep:@nextclaw/ncp-agent-runtime | AI (phantom-deps): Same-org dep likely dynamically loaded; stable FP. | ai | |
| phantom-deps | phantom-dep:@nextclaw/ncp-http-agent-server | AI (phantom-deps): Same-org dep likely dynamically loaded; stable FP. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-feishu | AI (phantom-deps): Listed as builtinExtension in nextclaw config; dynamically loaded. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-weixin | AI (phantom-deps): Listed as builtinExtension in nextclaw config; dynamically loaded. | ai | |
| phantom-deps | phantom-dep:@nextclaw/nextclaw-hermes-acp-bridge | AI (phantom-deps): Same-org dep likely dynamically loaded; stable FP. | ai | |
| phantom-deps | phantom-dep:@nextclaw/nextclaw-ncp-runtime-http-client | AI (phantom-deps): Same-org dep likely dynamically loaded; stable FP. | ai | |
| phantom-deps | phantom-dep:@nextclaw/nextclaw-ncp-runtime-stdio-client | AI (phantom-deps): Same-org dep likely dynamically loaded; stable FP. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.2.11 | 28 / 5 | |
| 0.1.20 | 27 / 5 | |
| 0.1.19 | 27 / 5 | |
| 0.1.18 | 27 / 5 | |
| 0.1.17 | 21 / 5 | |
| 0.1.16 | 21 / 5 | |
| 0.1.15 | 21 / 5 | |
| 0.1.14 | 21 / 5 | |
| 0.1.13 | 21 / 5 | |
| 0.1.12 | 21 / 5 | |
| 0.1.11 | 22 / 5 | |
| 0.1.10 | 22 / 5 | |
| 0.1.9 | 22 / 5 | |
| 0.1.8 | 22 / 5 | |
| 0.1.7 | 21 / 5 | |
| 0.1.6 | 21 / 5 | |
| 0.1.5 | 21 / 5 | |
| 0.1.4 | 21 / 5 | |
| 0.1.3 | 21 / 5 | |
| 0.1.2 | 21 / 5 | |
| 0.1.1 | 21 / 5 |
v0.2.11
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.