@nextclaw/kernel
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-extension-feishu | AI (phantom-deps): Same org scope; declared as dep but may be used indirectly or conditionally — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@nextclaw/channel-extension-weixin | AI (phantom-deps): Same org scope; declared as dep but may be used indirectly or conditionally — stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are @nextclaw-namespaced first-party packages from the same publisher ecosystem. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase attributable to bundling 12 new first-party @nextclaw deps, not injected payloads. | ai | |
| dependencies | unvetted-dep:@nextclaw/shared | AI (dependencies): Same @nextclaw org as publisher with 39 approved packages; stable false positive for this package family. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 15 / 4 | |
| 0.3.3 | 15 / 4 | |
| 0.3.2 | 15 / 4 | |
| 0.3.1 | 15 / 4 | |
| 0.3.0 | 15 / 4 | |
| 0.2.5 | 15 / 4 | |
| 0.2.4 | 15 / 4 | |
| 0.2.3 | 15 / 4 | |
| 0.2.2 | 15 / 4 | |
| 0.2.1 | 15 / 4 | |
| 0.2.0 | 15 / 4 | |
| 0.1.17 | 15 / 4 | |
| 0.1.16 | 15 / 4 | |
| 0.1.15 | 15 / 4 | |
| 0.1.14 | 14 / 4 | |
| 0.1.13 | 14 / 4 | |
| 0.1.12 | 14 / 4 | |
| 0.1.11 | 14 / 4 | |
| 0.1.10 | 14 / 4 | |
| 0.1.9 | 14 / 4 | |
| 0.1.8 | 13 / 4 | |
| 0.1.7 | 13 / 4 | |
| 0.1.6 | 13 / 4 | |
| 0.1.5 | 13 / 4 | |
| 0.1.4 | 13 / 4 | |
| 0.1.3 | 13 / 4 | |
| 0.1.2 | 1 / 4 | |
| 0.1.1 | 1 / 3 |
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.