@abstraxn/core-types MIT 2 versions

@abstraxn/core-types

npm

Abstraxn Client SDK types

Versions

MIT

License

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

jaskaran449sandeep_sjpankaj829

Keywords

EthereumGnosisAbstraxnSDK

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@ethersproject/bignumber	AI (phantom-deps): Transitively imported via ethers; declared as direct dependency for type safety.	ai	2026/04/29
phantom-deps	phantom-dep:@ethersproject/contracts	AI (phantom-deps): Transitively imported via ethers; declared as direct dependency for type safety.	ai	2026/04/29
phantom-deps	phantom-dep:@ethersproject/providers	AI (phantom-deps): Transitively imported via ethers; declared as direct dependency for type safety.	ai	2026/04/29

Versions (showing 2 of 2)

Version	Deps	Published
0.0.17	4 / 8	2026-01-08
0.0.16	4 / 8	2025-06-06

v0.0.16

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.