@wormhole-labs/base-bridge-executor-route Apache-2.0 11 versions

@wormhole-labs/base-bridge-executor-route

npm Repository Homepage

Wormhole SDK Route for Base-Solana bridge with executor service

11

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

evan-graytonyjinkev1n-peters

Keywords

wormholesdktypescriptconnect

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@mysten/sui	AI (phantom-deps): Declared as direct dep; likely used transitively or via config — stable false positive for this package.	ai	2026/05/21
phantom-deps	phantom-dep:@coral-xyz/anchor	AI (phantom-deps): Declared as direct dep; likely used transitively or via config — stable false positive for this package.	ai	2026/05/21
phantom-deps	phantom-dep:@aptos-labs/ts-sdk	AI (phantom-deps): Declared as direct dep; likely used transitively or via config — stable false positive for this package.	ai	2026/05/21

Versions (showing 11 of 11)

Version	Deps	Published
2.0.2	8 / 14	2026-05-20
2.0.1	8 / 14	2026-05-01
2.0.0	8 / 5	2026-04-28
1.0.7	8 / 5	2026-03-13
1.0.6	8 / 5	2026-02-17
1.0.5	8 / 5	2026-02-11
1.0.4	8 / 5	2026-01-14
1.0.3	8 / 5	2026-01-09
1.0.2	8 / 5	2026-01-09
1.0.1	8 / 5	2026-01-09
1.0.0	8 / 5	2026-01-08

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.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.

v2.0.0

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.

v1.0.7

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.

v1.0.6

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.

v1.0.5

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.

v1.0.4

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.

v1.0.3

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.

v1.0.2

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.

v1.0.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.

v1.0.0

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.