@tezos-domains/taquito-client
A library for interacting with tezos blockchain using taquito.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tezos-domains/core | AI (phantom-deps): Same-org scope dep, re-exported or used internally; stable FP. | ai | |
| phantom-deps | phantom-dep:@tezos-domains/manager | AI (phantom-deps): Same-org scope dep, re-exported or used internally; stable FP. | ai | |
| phantom-deps | phantom-dep:@tezos-domains/taquito | AI (phantom-deps): Same-org scope dep, re-exported or used internally; stable FP. | ai | |
| phantom-deps | phantom-dep:@tezos-domains/resolver | AI (phantom-deps): Same-org scope dep, re-exported or used internally; stable FP. | ai | |
| phantom-deps | phantom-dep:node-cache | AI (phantom-deps): node-cache is a declared runtime dependency; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): bignumber.js is a declared runtime dependency; phantom-dep heuristic is a false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.34.1 | 6 / 15 | |
| 1.34.0 | 6 / 15 | |
| 1.33.1 | 6 / 15 | |
| 1.33.0 | 6 / 15 | |
| 1.32.0 | 6 / 15 | |
| 1.31.0 | 6 / 15 | |
| 1.30.2 | 6 / 15 | |
| 1.30.1 | 6 / 15 | |
| 1.30.0 | 6 / 15 | |
| 1.29.0 | 6 / 15 | |
| 1.10.0 | 6 / 14 | |
| 1.9.0 | 6 / 14 | |
| 1.8.0 | 6 / 14 | |
| 1.7.0 | 6 / 14 | |
| 1.6.0 | 6 / 14 | |
| 1.5.0 | 6 / 14 | |
| 1.4.0 | 6 / 14 | |
| 1.3.0 | 6 / 14 | |
| 1.2.0 | 6 / 14 | |
| 1.1.0 | 6 / 14 | |
| 1.0.0 | 6 / 14 |
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
2 findingsThis version was published by a different npm account (roxin.cernica) than the most recent previously approved version (necroskillz) on 2021-12-28. It has since remained available on npm for 1669 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.