@fuel-ts/hasher
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@fuel-ts/crypto | AI (phantom-deps): Declared sibling dep in same org scope; phantom-dep heuristic is a stable false positive for this monorepo package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.103.0 | 3 / 0 | |
| 0.102.0 | 3 / 0 | |
| 0.101.3 | 3 / 0 | |
| 0.101.2 | 3 / 0 | |
| 0.101.1 | 3 / 0 | |
| 0.101.0 | 3 / 0 | |
| 0.100.6 | 3 / 0 | |
| 0.100.5 | 3 / 0 | |
| 0.100.4 | 3 / 0 | |
| 0.100.3 | 3 / 0 | |
| 0.100.2 | 3 / 0 | |
| 0.100.1 | 3 / 0 | |
| 0.100.0 | 3 / 0 | |
| 0.99.0 | 3 / 0 | |
| 0.98.0 | 3 / 0 | |
| 0.97.2 | 4 / 0 | |
| 0.97.1 | 4 / 0 | |
| 0.97.0 | 4 / 0 | |
| 0.96.1 | 4 / 0 | |
| 0.96.0 | 4 / 0 | |
| 0.95.0 | 4 / 0 | |
| 0.94.9 | 4 / 0 | |
| 0.94.8 | 4 / 0 | |
| 0.94.7 | 4 / 0 | |
| 0.94.6 | 4 / 0 | |
| 0.94.5 | 4 / 0 | |
| 0.94.4 | 4 / 0 | |
| 0.94.3 | 4 / 0 | |
| 0.94.2 | 4 / 0 | |
| 0.94.1 | 4 / 0 | |
| 0.94.0 | 4 / 0 | |
| 0.93.0 | 4 / 0 | |
| 0.92.1 | 4 / 0 | |
| 0.92.0 | 4 / 0 | |
| 0.91.0 | 4 / 0 | |
| 0.90.0 | 4 / 0 | |
| 0.89.2 | 4 / 0 | |
| 0.89.1 | 4 / 0 | |
| 0.89.0 | 4 / 0 | |
| 0.88.1 | 4 / 0 | |
| 0.88.0 | 4 / 0 | |
| 0.87.0 | 4 / 0 |
v0.100.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.98.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.97.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.97.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.88.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.