@fuel-ts/address
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fuel-ts/utils | AI (dependencies): Same-monorepo sibling dep at matching version; expected pattern for @fuel-ts/* packages. | ai | |
| dependencies | unvetted-dep:@fuel-ts/crypto | AI (dependencies): Same-monorepo sibling dep at matching version; expected pattern for @fuel-ts/* packages. | ai | |
| dependencies | unvetted-dep:@fuel-ts/errors | AI (dependencies): Same-monorepo sibling dep at matching version; expected pattern for @fuel-ts/* packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.103.0 | 4 / 0 | |
| 0.102.0 | 4 / 0 | |
| 0.101.3 | 4 / 0 | |
| 0.101.2 | 4 / 0 | |
| 0.101.1 | 4 / 0 | |
| 0.101.0 | 4 / 0 |
v0.103.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.102.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.101.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.101.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.101.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.101.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.