nostr-tools
Tools for making a Nostr client.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are nostr-wasm and @noble/ciphers — both legitimate, well-known packages in the Nostr/cryptography ecosystem, consistent with this package's purpose. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by bundled WASM binary from nostr-wasm and additional cipher implementations from @noble/ciphers in dual ESM/CJS build output. | ai | |
| source-diff | large-new-source-files | AI (source-diff): nostr-tools ships compiled ESM+CJS+types output; adding nostr-wasm (WASM binary) and @noble/ciphers naturally multiplies file count. No malicious indicators. | ai | |
| phantom-deps | phantom-dep:mitata | AI (phantom-deps): mitata is a dev/benchmark tool declared in dependencies but not imported; this is a packaging hygiene issue, not a security concern. | ai | |
| dependencies | unvetted-dep:mitata | AI (dependencies): mitata is a benchmarking library accidentally placed in dependencies instead of devDependencies; it is not imported at runtime (confirmed by phantom-dep finding) and poses no security risk. | ai | |
| dependencies | unvetted-dep:nostr-wasm | AI (dependencies): nostr-wasm is a WASM binding for Nostr secp256k1 operations, directly relevant to nostr-tools' purpose and maintained by the same ecosystem. | ai | |
| dependencies | unvetted-dep:@noble/ciphers | AI (dependencies): @noble/ciphers is from Paul Miller's well-audited @noble cryptography suite, consistent with the other @noble deps already accepted in this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): The dormancy is an artifact of comparing v2.23.3 against the old v1.13.1 baseline. This is a major version rewrite by the original author, not an account takeover. | ai | |
| dependencies | unvetted-dep:@noble/curves | AI (dependencies): @noble/curves is a reputable cryptographic library by Paul Miller, expected for a Nostr client that uses secp256k1. Stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): nostr-tools is an established, well-known Nostr protocol library; lack of Sigstore provenance is common and not a risk signal for this package. | ai |
Versions (showing 51 of 121)
| Version | Deps | Published |
|---|---|---|
| 2.23.5 | 7 / 14 | |
| 2.23.4 | 7 / 14 | |
| 2.23.3 | 7 / 14 | |
| 2.23.2 | 7 / 14 | |
| 2.23.1 | 7 / 14 | |
| 2.23.0 | 7 / 14 | |
| 2.22.1 | 7 / 14 | |
| 2.22.0 | 7 / 14 | |
| 2.21.0 | 7 / 14 | |
| 2.20.0 | 7 / 14 | |
| 2.19.4 | 7 / 14 | |
| 2.19.3 | 7 / 14 | |
| 2.19.2 | 7 / 14 | |
| 2.19.1 | 7 / 14 | |
| 2.19.0 | 7 / 14 | |
| 2.18.2 | 7 / 14 | |
| 2.18.1 | 7 / 14 | |
| 2.18.0 | 7 / 14 | |
| 2.17.4 | 7 / 14 | |
| 2.17.3 | 7 / 14 | |
| 2.17.2 | 7 / 14 | |
| 2.17.1 | 7 / 14 | |
| 2.17.0 | 7 / 14 | |
| 2.16.2 | 7 / 14 | |
| 2.16.1 | 7 / 14 | |
| 2.16.0 | 7 / 14 | |
| 2.15.2 | 7 / 14 | |
| 2.15.1 | 7 / 14 | |
| 2.15.0 | 7 / 14 | |
| 2.14.3 | 7 / 14 | |
| 2.14.2 | 7 / 14 | |
| 2.14.1 | 7 / 14 | |
| 2.14.0 | 7 / 14 | |
| 2.13.3 | 7 / 14 | |
| 2.13.2 | 7 / 14 | |
| 2.13.1 | 7 / 14 | |
| 2.13.0 | 6 / 14 | |
| 2.12.0 | 6 / 18 | |
| 2.11.1 | 6 / 18 | |
| 2.11.0 | 6 / 18 | |
| 2.10.4 | 6 / 18 | |
| 2.10.3 | 6 / 18 | |
| 2.10.2 | 6 / 18 | |
| 2.10.1 | 6 / 18 | |
| 2.10.0 | 6 / 18 | |
| 2.9.4 | 6 / 18 | |
| 2.9.3 | 6 / 18 | |
| 2.9.2 | 6 / 18 | |
| 2.9.1 | 6 / 18 | |
| 2.9.0 | 6 / 18 | |
| 2.8.1 | 6 / 18 |
v2.23.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.