@defuse-protocol/bridge-sdk No license 19 versions

@defuse-protocol/bridge-sdk

npm

19

Versions

—

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

auroraseccawabunga_aurora

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:viem	AI (phantom-deps): viem is a declared runtime dependency in package.json; phantom-dep is a false positive for this package.	ai	2026/05/13
phantom-deps	phantom-dep:ethers	AI (phantom-deps): ethers is a declared runtime dependency in package.json; phantom-dep is a false positive for this package.	ai	2026/05/13
phantom-deps	phantom-dep:borsher	AI (phantom-deps): borsher is a declared runtime dependency in package.json; phantom-dep is a false positive for this package.	ai	2026/05/13
phantom-deps	phantom-dep:near-api-js	AI (phantom-deps): near-api-js is a declared runtime dependency in package.json; phantom-dep is a false positive for this package.	ai	2026/05/13

Versions (showing 19 of 19)

Version	Deps	Published
0.13.2	9 / 3	2025-08-06
0.13.1	9 / 3	2025-08-06
0.13.0	9 / 3	2025-08-06
0.12.0	9 / 3	2025-08-05
0.11.2	9 / 3	2025-08-05
0.11.1	9 / 3	2025-08-04
0.11.0	9 / 3	2025-07-31
0.10.3	9 / 3	2025-07-24
0.10.2	9 / 3	2025-07-24
0.10.1	9 / 3	2025-07-23
0.10.0	9 / 3	2025-07-23
0.9.0	9 / 4	2025-07-22
0.8.1	8 / 3	2025-07-16
0.8.0	8 / 3	2025-07-16
0.7.6	8 / 3	2025-07-15
0.7.5	8 / 3	2025-07-14
0.1.1	7 / 4	2025-06-18
0.0.2	9 / 3	2025-06-17
0.0.1	9 / 3	2025-06-17

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.2

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.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.

v0.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.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.

v0.7.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.

v0.1.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.

v0.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.

v0.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.