@fuel-ts/program
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.global.js | AI (source-diff): Base64-embedded WASM binary for @fuels/vm-asm bundling, not obfuscated payload. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo lockstep release cadence from trusted fuel-ci publisher, not takeover indicator. | ai | |
| provenance | no-provenance | AI (provenance): Fuel Labs monorepo CI publisher; no provenance is consistent across all their releases. | ai | |
| dependencies | unvetted-dep:@fuel-ts/account | AI (dependencies): Sibling monorepo package from FuelLabs; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@fuel-ts/address | AI (dependencies): Sibling monorepo package from FuelLabs; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@fuel-ts/math | AI (dependencies): Sibling monorepo package from FuelLabs; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@fuel-ts/transactions | AI (dependencies): Sibling monorepo package from FuelLabs; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@fuel-ts/abi-coder | AI (dependencies): Sibling monorepo package from FuelLabs; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@fuel-ts/utils | AI (dependencies): Sibling monorepo package from FuelLabs; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@fuel-ts/errors | AI (dependencies): Sibling monorepo package from FuelLabs; coordinated versioning is expected. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.103.0 | 9 / 1 | |
| 0.101.1 | 9 / 1 | |
| 0.101.0 | 9 / 1 | |
| 0.100.6 | 9 / 1 | |
| 0.100.5 | 9 / 1 | |
| 0.100.4 | 9 / 1 | |
| 0.100.3 | 9 / 1 | |
| 0.100.2 | 9 / 1 | |
| 0.100.1 | 9 / 1 | |
| 0.100.0 | 9 / 1 | |
| 0.99.0 | 9 / 1 | |
| 0.98.0 | 9 / 1 | |
| 0.97.2 | 10 / 1 | |
| 0.97.1 | 10 / 1 |
v0.100.6
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.5
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.4
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.2
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.98.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.