ably — Greenflagged

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

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:build/ably.noencryption.min.js	AI (source-diff): Minified webpack bundle; benign.	ai	2026/07/08
source-diff	net-exec-file:build/ably-commonjs.js	AI (source-diff): Realtime lib bundle; network+eval is normal for webpack runtime, no hostile target.	ai	2026/07/08
source-diff	obfuscated-file:build/ably-commonjs.noencryption.js	AI (source-diff): Webpack bundle output; minified, not obfuscated.	ai	2026/07/08
source-diff	net-exec-file:build/ably-commonjs.noencryption.js	AI (source-diff): Bundled realtime library artifact; benign.	ai	2026/07/08
source-diff	net-exec-file:build/ably-webworker.min.js	AI (source-diff): Minified webpack worker bundle; benign.	ai	2026/07/08
source-diff	obfuscated-file:build/ably.noencryption.js	AI (source-diff): Webpack bundle output; not obfuscation.	ai	2026/07/08
source-diff	net-exec-file:build/ably.noencryption.js	AI (source-diff): Bundled realtime library artifact; benign.	ai	2026/07/08
source-diff	obfuscated-file:build/ably-commonjs.js	AI (source-diff): Webpack bundle output with Ably license banner; not obfuscation.	ai	2026/07/08
publish-pattern	dormant-publish	AI (publish-pattern): Ably publishes frequently; dormancy flag is a false positive for this active package.	ai	2026/06/06
npm-metadata	url-dep:async	AI (npm-metadata): Points to ably-forks/async on GitHub; stable fork management pattern for this package.	ai	2026/06/06
npm-metadata	url-dep:esbuild-plugin-umd-wrapper	AI (npm-metadata): Points to ably-forks org; consistent fork management pattern, devDependency only.	ai	2026/06/06
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	2026/04/25
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	2026/04/25
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	2026/04/25

Versions (showing 40 of 40)

Version	Deps	Published
2.26.0	6 / 64	2026-07-23
2.25.0	6 / 64	2026-07-17
2.24.0	6 / 64	2026-07-09
2.23.0	6 / 64	2026-06-19
2.22.1	6 / 62	2026-06-08
2.22.0	6 / 62	2026-06-05
2.21.0	6 / 62	2026-03-19
2.20.0	6 / 62	2026-03-13
2.19.0	6 / 62	2026-03-03
2.18.0	6 / 62	2026-02-23
2.17.1	6 / 62	2026-01-30
2.17.0	6 / 62	2026-01-08
2.16.0	6 / 62	2025-12-19
2.15.0	6 / 62	2025-12-02
2.14.0	6 / 62	2025-10-02
2.12.0	6 / 62	2025-08-22
2.11.1	6 / 62	2025-08-21
2.11.0	6 / 62	2025-08-13
2.10.1	6 / 62	2025-07-16
2.10.0	6 / 62	2025-06-25
2.9.0	6 / 62	2025-05-08
2.8.0	5 / 62	2025-05-01
2.6.5	5 / 62	2025-03-24
2.6.4	5 / 62	2025-03-17
2.6.3	5 / 62	2025-01-28
2.6.2	5 / 62	2025-01-14
2.6.0	5 / 62	2024-12-10
2.4.1	5 / 62	2024-10-04
2.4.0	5 / 62	2024-09-11
2.3.2	5 / 62	2024-09-06
2.3.1	5 / 62	2024-07-30
2.3.0	5 / 60	2024-07-10
2.2.1	4 / 60	2024-07-02
2.2.0	4 / 60	2024-06-24
2.1.0	4 / 60	2024-06-03
2.0.4	4 / 60	2024-05-03
2.0.3	4 / 60	2024-04-18
2.0.2	4 / 60	2024-04-09
2.0.1	4 / 60	2024-03-25
2.0.0	3 / 60	2024-03-22

v2.26.0

1 finding

LOW No provenance attestation provenance

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

v2.25.0

1 finding

LOW No provenance attestation provenance

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

v2.24.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: andrii.bulat.ably → ttypic (on 2026-07-09, known maintainer) provenance

This version was published by a different npm account (ttypic) than the most recent previously approved version (andrii.bulat.ably) on 2026-07-09, but ttypic is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.6.5

1 finding

LOW No provenance attestation provenance

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

v2.6.4

1 finding

LOW No provenance attestation provenance

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

v2.6.3

1 finding

LOW No provenance attestation provenance

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

v2.6.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: andrii.bulat.ably → splind06 (on 2025-01-14, known maintainer) provenance

This version was published by a different npm account (splind06) than the most recent previously approved version (andrii.bulat.ably) on 2025-01-14, but splind06 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ttypic → andrii.bulat.ably (on 2024-09-11, known maintainer) provenance

This version was published by a different npm account (andrii.bulat.ably) than the most recent previously approved version (ttypic) on 2024-09-11, but andrii.bulat.ably is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.3.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ttypic → andrii.bulat.ably (on 2024-09-06, known maintainer) provenance

This version was published by a different npm account (andrii.bulat.ably) than the most recent previously approved version (ttypic) on 2024-09-06, but andrii.bulat.ably is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.3.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: andrii.bulat.ably → ttypic (on 2024-07-30, known maintainer) provenance

This version was published by a different npm account (ttypic) than the most recent previously approved version (andrii.bulat.ably) on 2024-07-30, but ttypic is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.3.0

10 findings

HIGH New obfuscated file: build/ably-commonjs.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: build/ably-commonjs.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: build/ably-commonjs.noencryption.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: build/ably-commonjs.noencryption.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: build/ably-webworker.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: build/ably.noencryption.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: build/ably.noencryption.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: build/ably.noencryption.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

INFO Publisher changed: andrii.bulat.ably → owenpearson (on 2024-07-10, known maintainer) provenance

This version was published by a different npm account (owenpearson) than the most recent previously approved version (andrii.bulat.ably) on 2024-07-10, but owenpearson is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

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.