@metamask/sdk-communication-layer No license 3 versions

@metamask/sdk-communication-layer

npm Repository Homepage

Versions

—

License

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

danfinlaykumavismcmirerekmarksmetamaskbotgudahttnicholasellulsethkfmannaugtur

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:date-fns	AI (phantom-deps): Declared dependency; referenced in config files for optional/transitive use.	ai	2026/04/28
phantom-deps	phantom-dep:bufferutil	AI (phantom-deps): Declared dependency; referenced in lavamoat config for ws optional binding.	ai	2026/04/28
phantom-deps	phantom-dep:utf-8-validate	AI (phantom-deps): Declared dependency; referenced in lavamoat config for ws optional binding.	ai	2026/04/28

Versions (showing 3 of 3)

Version	Deps	Published
0.33.1	6 / 47	2025-09-11
0.33.0	6 / 47	2025-05-21
0.15.0	8 / 35	2024-02-15

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