@fuel-ts/abi-coder
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Fuel Labs monorepo packages consistently lack provenance; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@fuel-ts/math | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@fuel-ts/utils | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@fuel-ts/crypto | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@fuel-ts/errors | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@fuel-ts/hasher | AI (dependencies): Sibling monorepo package released in lockstep; not an independent risk. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.103.0 | 6 / 0 | |
| 0.102.0 | 6 / 0 | |
| 0.101.3 | 6 / 0 | |
| 0.101.2 | 6 / 0 | |
| 0.101.1 | 6 / 0 | |
| 0.101.0 | 6 / 0 | |
| 0.100.6 | 6 / 0 | |
| 0.100.5 | 6 / 0 | |
| 0.100.4 | 6 / 0 | |
| 0.100.3 | 6 / 0 | |
| 0.100.2 | 6 / 0 | |
| 0.100.1 | 6 / 0 | |
| 0.100.0 | 6 / 0 | |
| 0.99.0 | 6 / 0 | |
| 0.98.0 | 6 / 0 | |
| 0.97.2 | 7 / 0 | |
| 0.97.1 | 7 / 0 | |
| 0.97.0 | 7 / 0 | |
| 0.96.1 | 7 / 0 | |
| 0.96.0 | 7 / 0 | |
| 0.95.0 | 7 / 0 | |
| 0.94.9 | 7 / 0 | |
| 0.94.8 | 7 / 0 | |
| 0.94.7 | 7 / 0 | |
| 0.94.6 | 7 / 0 | |
| 0.94.5 | 7 / 0 | |
| 0.94.4 | 7 / 0 | |
| 0.94.3 | 7 / 0 | |
| 0.94.2 | 7 / 0 | |
| 0.94.1 | 7 / 0 | |
| 0.94.0 | 7 / 0 | |
| 0.93.0 | 7 / 0 | |
| 0.92.1 | 7 / 0 | |
| 0.92.0 | 7 / 0 | |
| 0.91.0 | 7 / 0 | |
| 0.90.0 | 7 / 0 | |
| 0.89.2 | 7 / 0 | |
| 0.89.1 | 7 / 0 | |
| 0.89.0 | 7 / 0 | |
| 0.88.1 | 7 / 0 | |
| 0.88.0 | 7 / 0 | |
| 0.87.0 | 7 / 0 |
v0.100.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.97.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.97.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.97.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.95.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.88.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.88.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.87.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.