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
{{ message }}
Repository navigation
Remove the noscript pixel from the SRI embed script - #92
v12 is the latest scripts release, and sri/v13.js returns 404. The CDN file matches dist/v12/app.js in the v12 release except for the source-map filename, which the deploy step renames.
Before: the code block in the built _site/sri.html shows the script and the noscript.gif pixel. After:jekyll build succeeds, and the code block shows only the script with the same hashes. The page's only remaining noscript.gif is the docs site's own tracking tag from _layouts/default.html.
Security implications
No security impact
Has security impact - described as:
Merge Danger
Door: two-way
Blast Radius: one page
New SRI installs copied from this page won't include the pixel, so they won't record page views from visitors without JavaScript. Existing installs are unaffected.
Summary by CodeRabbit
Documentation
The SRI embed example now shows only the script tag; the <noscript> image fallback has been removed.
The pixel has nothing to do with SRI and mostly records bots. The
published hashes still match sri/v12.js on the CDN.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This is a documentation-only change that removes the noscript pixel from the SRI embed example, as requested. Existing installs are unaffected. It is safe to merge.
Pre-merge checks: 4
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title "Remove the noscript pixel from the SRI embed script" matches the only change in the changeset. The raw summary shows that the SRI embed example in _docs/20_install-script/19_sri.md no longe…
Linked Issues check
Issue #91 asks to remove the <noscript> pixel from the SRI embed script on the SRI page. The whole-PR diff (merge base a25857a to head 079eec7) removes exactly that line from `_docs/20_install-scr…
Out of Scope Changes check
The only change in the whole PR is the one-line removal of the <noscript> pixel from _docs/20_install-script/19_sri.md. This is the file and element named in #91. No other install pages are modifi…
Full details: Title check
Explanation
The title "Remove the noscript pixel from the SRI embed script" matches the only change in the changeset. The raw summary shows that the SRI embed example in _docs/20_install-script/19_sri.md no longer includes the noscript image fallback, leaving only the script tag. The objectives confirm the same scope: removing the noscript tracking pixel from the SRI page embed example, with the integrity hashes unchanged. The title is specific, concise, and describes the primary change.
Full details: Linked Issues check
Explanation
Issue #91 asks to remove the <noscript> pixel from the SRI embed script on the SRI page. The whole-PR diff (merge base a25857a to head 079eec7) removes exactly that line from _docs/20_install-script/19_sri.md. The embed block now contains only the <script async src=".../sri/v{{ page.sriVersion }}.js" integrity="{{ page.sriHash }}" crossorigin="anonymous"> tag. The diff does not change sriHash or sriVersion. The hash check in #91 is a verification step. The author reports that the hashes match sri/v12.js. The repository tools cannot fetch the live CDN file, so the hash match is not independently verified here. No code change is needed for that step unless the hashes differ. The coding requirement is met.
Full details: Out of Scope Changes check
Explanation
The only change in the whole PR is the one-line removal of the <noscript> pixel from _docs/20_install-script/19_sri.md. This is the file and element named in #91. No other install pages are modified. The issue explicitly excludes other install pages that show the pixel, and this PR leaves them unchanged. No unrelated changes were found.
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: QUIET
Plan: Team
Run ID: 0b08ca5d-ac51-4148-b32e-09912ab74692
Commits
Reviewing files that changed from the base of the PR and between a25857a and 079eec7.
Files selected for processing: 1
_docs/20_install-script/19_sri.md
Files with no reviewable changes: 1
_docs/20_install-script/19_sri.md
Included review availability: This review used your included allowance. 4 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 8 reviews per hour.
SDLC label: change: routine because The change removes a noscript tracking-pixel snippet from a public documentation page, which is a static docs site and always routine, so no one's data access or production behavior is affected.
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
change: routineRoutine or ordinary change that needs at most one human or AI-assisted review
2 participants
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.
Summary
Closes #91
Removes the
<noscript>pixel from the embed script on the SRI page. The integrity hashes are unchanged because they still match the live script.<script async src="https://scripts.simpleanalyticscdn.com/sri/v12.js" integrity="sha256-… sha384-… sha512-…" crossorigin="anonymous"></script> -<noscript><img src="https://queue.simpleanalyticscdn.com/noscript.gif" alt="" referrerpolicy="no-referrer-when-downgrade" /></noscript>Evidence
https://scripts.simpleanalyticscdn.com/sri/v12.js, and they match the page'ssriHash:sri/v13.jsreturns 404. The CDN file matchesdist/v12/app.jsin the v12 release except for the source-map filename, which the deploy step renames._site/sri.htmlshows the script and thenoscript.gifpixel.After:
jekyll buildsucceeds, and the code block shows only the script with the same hashes. The page's only remainingnoscript.gifis the docs site's own tracking tag from_layouts/default.html.Security implications
Merge Danger
Door: two-way
Blast Radius: one page
New SRI installs copied from this page won't include the pixel, so they won't record page views from visitors without JavaScript. Existing installs are unaffected.
Summary by CodeRabbit
<noscript>image fallback has been removed.