← Home

ably

npm Repository Homepage
17
Versions
—
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

owenpearsonsimonw_ablyttypiclawrence.forooghian.ablyandrii.bulat.ablyandytwfsplind06vlad.velici.ablyably-realtime

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Ably publishes frequently; dormancy flag is a false positive for this active package. ai
npm-metadata url-dep:async AI (npm-metadata): Points to ably-forks/async on GitHub; stable fork management pattern for this package. ai
npm-metadata url-dep:esbuild-plugin-umd-wrapper AI (npm-metadata): Points to ably-forks org; consistent fork management pattern, devDependency only. ai
semgrep semgrep:base64-decode AI (semgrep): Standard base64 decoding utility in a messaging SDK for protocol encoding/decoding. Not obfuscated; sourced from public Ably GitHub repo. Stable false positive for this package. ai
semgrep semgrep:hex-decode AI (semgrep): Standard hex decoding utility in a messaging SDK. Not obfuscated; sourced from public Ably GitHub repo. Stable false positive for this package. ai
dependencies unvetted-dep:@ably/msgpack-js AI (dependencies): @ably/msgpack-js is Ably's own first-party fork of msgpack-js under their org scope, used for MessagePack protocol serialization. Stable dependency for this package. ai

Versions (showing 17 of 17)

Version Deps Published
2.22.1 6 / 62
2.22.0 6 / 62
2.21.0 6 / 62
2.20.0 6 / 62
2.19.0 6 / 62
2.18.0 6 / 62
2.17.1 6 / 62
2.17.0 6 / 62
2.16.0 6 / 62
2.15.0 6 / 62
2.12.0 6 / 62
2.11.1 6 / 62
2.11.0 6 / 62
2.10.1 6 / 62
2.10.0 6 / 62
2.9.0 6 / 62
2.8.0 5 / 62

v2.22.1

1 finding
LOW No provenance attestation provenance

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

v2.22.0

1 finding
LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

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

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

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

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

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