@terminal3/t3n-sdk
T3n TypeScript SDK - A minimal SDK that mirrors the server's RPC handler approach
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
nik-t3edward-fu-t3matthew-t3jeff-t3phuc-t3trha
Keywords
t3nblockchainsdktypescriptwasmcryptographyauthentication
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): ethers is a well-known Ethereum library; its indirect use via WASM-generated or bundled code is consistent with this blockchain SDK's purpose. | ai | |
| phantom-deps | phantom-dep:@bytecodealliance/jco | AI (phantom-deps): jco is used as a build/runtime tool for WASM component model; indirect import via config/generated code is expected for this WASM SDK. | ai |
v1.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.