@fuel-ts/script
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): Encoded string is a base64 WASM binary for fuel-ts math/instruction processing; stable pattern across this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is expected pattern for fuel-ts packages. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Scoped @fuel-ts/* package from FuelLabs monorepo; levenshtein match to bcrypt is a false positive. | ai | |
| typosquat | typosquat.levenshtein:stripe | AI (typosquat): Scoped @fuel-ts/* package from FuelLabs monorepo; levenshtein match to stripe is a false positive. | ai | |
| phantom-deps | phantom-dep:@fuel-ts/transactions | AI (phantom-deps): Same-org sibling dep; may be used transitively or in type declarations without direct import. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.103.0 | 7 / 1 | |
| 0.102.0 | 7 / 1 | |
| 0.101.3 | 7 / 1 | |
| 0.101.2 | 7 / 1 | |
| 0.101.1 | 7 / 1 | |
| 0.101.0 | 7 / 1 |
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
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.