You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds optional @scanly/url-safety with local URL signals, canonicalization/redaction, bounded cache and single-flight ownership, a browser-safe client/controller, DNS-pinned SSRF-protected server inspection, lookup-only reputation adapters, structured advisory LLM integration, and deterministic authority-aware scoring. Demo URL intelligence is disabled by default; barcode images/frames never enter the network layer.
All GitHub workflows on this source passed, including CI, Full Benchmark, Browser Benchmark, Tracking Benchmark, Industrial Benchmark, Public API, Device Evidence Validation and Native Mobile. This includes actual Worker/WASM soak, iOS, Android emulator, Native Core and Native Memory qualification; it does not claim physical-device validation.
Local evidence includes 148 URL safety tests (65 SSRF tests), 46/19/19 browser E2E, 48 browser benchmark cases, a 1,000-frame actual Worker/WASM soak, full Realtime/Tracking/Industrial gates, package import and installed-tarball/type/browser-boundary smoke, and PUBLIC_API_2_1_GO. Coverage thresholds were not lowered. Source/evidence Git fixture timeouts alone use a bounded 30-second budget on slow Windows hosts; decoder/security deadlines are unchanged.
The final same-machine URL benchmark observed baseline/current decoder medians 270.17/268.86 ms, local analysis P95 0.090 ms, and one remote call for 100 repeated URLs. Reports are development/feature qualification, not a publication record.
Release blocked — no publication claim
Local npm authentication returns 401 and @scanly/url-safety is not currently retrievable from the registry (404). Fresh 11-package publishing/Trusted Publisher credentials must be verified. Candidate artifact/reproducibility/signing evidence and the guarded Stable manifest must be finalized before any signed v2.1.0 tag or publication. No tag, GitHub Release or npm artifact was published by this PR.
v2.0.0/v2.0.1 tags, manifests, releases, artifact bytes, SBOMs, checksums and publication records are unchanged. Issue #13 remains independent and open.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scanly 2.1.0 — Link Intelligence
Adds optional @scanly/url-safety with local URL signals, canonicalization/redaction, bounded cache and single-flight ownership, a browser-safe client/controller, DNS-pinned SSRF-protected server inspection, lookup-only reputation adapters, structured advisory LLM integration, and deterministic authority-aware scoring. Demo URL intelligence is disabled by default; barcode images/frames never enter the network layer.
Qualified feature source
SOURCE_SHA: bdf9e55
TREE_SHA: c72430a2ab0a2d47e7cd095325088f1e053a5c41
BASE_SHA: f0d10d2
All GitHub workflows on this source passed, including CI, Full Benchmark, Browser Benchmark, Tracking Benchmark, Industrial Benchmark, Public API, Device Evidence Validation and Native Mobile. This includes actual Worker/WASM soak, iOS, Android emulator, Native Core and Native Memory qualification; it does not claim physical-device validation.
Local evidence includes 148 URL safety tests (65 SSRF tests), 46/19/19 browser E2E, 48 browser benchmark cases, a 1,000-frame actual Worker/WASM soak, full Realtime/Tracking/Industrial gates, package import and installed-tarball/type/browser-boundary smoke, and PUBLIC_API_2_1_GO. Coverage thresholds were not lowered. Source/evidence Git fixture timeouts alone use a bounded 30-second budget on slow Windows hosts; decoder/security deadlines are unchanged.
The final same-machine URL benchmark observed baseline/current decoder medians 270.17/268.86 ms, local analysis P95 0.090 ms, and one remote call for 100 repeated URLs. Reports are development/feature qualification, not a publication record.
Release blocked — no publication claim
Local npm authentication returns 401 and @scanly/url-safety is not currently retrievable from the registry (404). Fresh 11-package publishing/Trusted Publisher credentials must be verified. Candidate artifact/reproducibility/signing evidence and the guarded Stable manifest must be finalized before any signed v2.1.0 tag or publication. No tag, GitHub Release or npm artifact was published by this PR.
v2.0.0/v2.0.1 tags, manifests, releases, artifact bytes, SBOMs, checksums and publication records are unchanged. Issue #13 remains independent and open.