@nextclaw/remote
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@nextclaw/kernel | AI (phantom-deps): Same-org dep (@nextclaw scope); likely re-exported or used transitively within the monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Young monorepo package; lack of provenance is common and no other risk signals present. | ai |
Versions (showing 51 of 139)
| Version | Deps | Published |
|---|---|---|
| 0.3.17 | 5 / 4 | |
| 0.3.16 | 5 / 4 | |
| 0.3.15 | 5 / 4 | |
| 0.3.14 | 5 / 4 | |
| 0.3.13 | 5 / 4 | |
| 0.3.12 | 5 / 4 | |
| 0.3.11 | 5 / 4 | |
| 0.3.10 | 5 / 4 | |
| 0.3.9 | 5 / 4 | |
| 0.3.8 | 5 / 4 | |
| 0.3.7 | 5 / 4 | |
| 0.3.6 | 5 / 4 | |
| 0.3.5 | 5 / 4 | |
| 0.3.4 | 5 / 4 | |
| 0.3.3 | 5 / 4 | |
| 0.3.2 | 5 / 4 | |
| 0.3.1 | 5 / 4 | |
| 0.3.0 | 5 / 4 | |
| 0.2.18 | 5 / 4 | |
| 0.2.17 | 5 / 4 | |
| 0.2.16 | 5 / 4 | |
| 0.2.15 | 5 / 4 | |
| 0.2.14 | 5 / 4 | |
| 0.2.13 | 5 / 4 | |
| 0.2.12 | 5 / 4 | |
| 0.2.11 | 5 / 4 | |
| 0.2.9 | 5 / 4 | |
| 0.2.8 | 5 / 4 | |
| 0.2.7 | 5 / 4 | |
| 0.2.6 | 5 / 4 | |
| 0.2.5 | 5 / 4 | |
| 0.2.4 | 5 / 4 | |
| 0.2.3 | 5 / 4 | |
| 0.2.2 | 5 / 4 | |
| 0.2.1 | 5 / 4 | |
| 0.2.0 | 5 / 4 | |
| 0.1.105 | 5 / 4 | |
| 0.1.104 | 5 / 4 | |
| 0.1.103 | 5 / 4 | |
| 0.1.102 | 5 / 4 | |
| 0.1.101 | 5 / 4 | |
| 0.1.100 | 5 / 4 | |
| 0.1.99 | 5 / 4 | |
| 0.1.98 | 5 / 4 | |
| 0.1.97 | 5 / 4 | |
| 0.1.96 | 5 / 4 | |
| 0.1.95 | 5 / 4 | |
| 0.1.94 | 5 / 4 | |
| 0.1.93 | 5 / 4 | |
| 0.1.92 | 5 / 4 | |
| 0.1.91 | 5 / 4 |
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.