← Home

@abtnode/client

npm Repository Homepage
15
Versions
—
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

wangshijunpolunzhmave99a

Keywords

graphqlclientarcblock

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@ocap/util AI (phantom-deps): Transitive dependency; stable pattern for this package. ai
phantom-deps phantom-dep:blueimp-md5 AI (phantom-deps): Transitive dependency; stable pattern for this package. ai
phantom-deps phantom-dep:axios AI (phantom-deps): Transitive dependency; stable pattern for this package. ai
phantom-deps phantom-dep:debug AI (phantom-deps): Transitive dependency; stable pattern for this package. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Transitive dependency; stable pattern for this package. ai
phantom-deps phantom-dep:react-app-polyfill AI (phantom-deps): Transitive dependency; stable pattern for this package. ai

Versions (showing 15 of 15)

Version Deps Published
1.16.48 11 / 13
1.16.40 10 / 13
1.16.39 10 / 13
1.16.38 10 / 13
1.16.37 10 / 13
1.16.36 10 / 13
1.16.35 10 / 13
1.16.34 10 / 13
1.16.33 10 / 13
1.16.32 10 / 13
1.16.31 10 / 13
1.16.30 10 / 13
1.16.29 10 / 13
1.16.28 10 / 13
1.16.27 10 / 13

v1.16.40

1 finding
LOW No provenance attestation provenance

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

v1.16.39

1 finding
LOW No provenance attestation provenance

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

v1.16.38

1 finding
LOW No provenance attestation provenance

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

v1.16.37

1 finding
LOW No provenance attestation provenance

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

v1.16.36

1 finding
LOW No provenance attestation provenance

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

v1.16.35

1 finding
LOW No provenance attestation provenance

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

v1.16.34

1 finding
LOW No provenance attestation provenance

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

v1.16.33

1 finding
LOW No provenance attestation provenance

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

v1.16.32

1 finding
LOW No provenance attestation provenance

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

v1.16.31

1 finding
LOW No provenance attestation provenance

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

v1.16.30

1 finding
LOW No provenance attestation provenance

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

v1.16.29

1 finding
LOW No provenance attestation provenance

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

v1.16.28

1 finding
LOW No provenance attestation provenance

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

v1.16.27

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.