← Home

@abstraxn/core-types

npm

Abstraxn Client SDK types

11
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jaskaran449sandeep_sjpankaj829

Keywords

EthereumGnosisAbstraxnSDK

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@ethersproject/bignumber AI (phantom-deps): Transitively imported via ethers; declared as direct dependency for type safety. ai
phantom-deps phantom-dep:@ethersproject/contracts AI (phantom-deps): Transitively imported via ethers; declared as direct dependency for type safety. ai
phantom-deps phantom-dep:@ethersproject/providers AI (phantom-deps): Transitively imported via ethers; declared as direct dependency for type safety. ai

Versions (showing 11 of 11)

Version Deps Published
0.0.17 4 / 8
0.0.16 4 / 8
0.0.15 4 / 8
0.0.14 4 / 8
0.0.13 4 / 8
0.0.12 4 / 8
0.0.11 4 / 8
0.0.10 4 / 8
0.0.9 4 / 8
0.0.8 4 / 8
0.0.7 4 / 8

v0.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.8

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.0.7

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.