← Home

@eco-foundation/routes-ts

npm Repository Homepage

The Eco Routes Protocol is a decentralized intent based system that allows users to submit their intent to the network and have it fulfilled by a solver on the destination rollup of their choise.

9
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mdavid123seveyeconknavkalpagedaleph2012carlosfebres

Keywords

solidityethereumeco routesroutesbendprotocolrollupsolver

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/abi/contracts/Portal.d.ts AI (source-diff): Long hex string is EVM contract bytecode, a normal artifact in Solidity ABI packages. ai
source-diff encoded-string-file:dist/abi/contracts/Portal.js AI (source-diff): Long hex string is EVM contract bytecode, a normal artifact in Solidity ABI packages. ai

Versions (showing 9 of 9)

Version Deps Published
3.2.17 2 / 0
3.2.16 2 / 0
3.2.15 2 / 0
3.2.14 2 / 0
3.2.12 2 / 0
3.2.11 2 / 0
3.2.4 2 / 0
3.2.2 2 / 0
3.2.1 2 / 0

v3.2.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.4

3 findings
HIGH Long encoded string in modified file: dist/abi/contracts/Portal.d.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/abi/contracts/Portal.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.