Skip to content

chore(deps): bump snapsynapse/skill-a11y-audit/.github/actions/scan from 2.7.0 to 3.3.0 - #12

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/snapsynapse/skill-a11y-audit/dot-github/actions/scan-3.3.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/snapsynapse/skill-a11y-audit/dot-github/actions/scan-3.3.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 1, 2026

Copy link
Copy Markdown
Contributor

Bumps snapsynapse/skill-a11y-audit/.github/actions/scan from 2.7.0 to 3.3.0.

Release notes

Sourced from snapsynapse/skill-a11y-audit/.github/actions/scan's releases.

v3.3.0: Security execution defaults

Security release, 2026-10-26. Published tag, asset and hosting evidence is maintained in the repository release record.

Security fixes

  • SEC-001: Dependency checks reject unavailable, malformed and inconsistent npm audit reports. Valid reports remain usable when npm's configured severity threshold produces exit 0 with nonblocking advisories.
  • SEC-002: Discovery excludes unapproved sitemap targets; direct sitemap scanning rejects unapproved leaves, child documents and redirects. Scanner top-level navigation and redirects are confined to approved origins. Plan metadata cannot grant new permission.
  • SEC-003: Chromium sandboxing is enabled by default. An explicit override is available for a separately isolated runner; there is no silent fallback.
  • SEC-004: The temporary Action server binds to loopback, disables directory listings and refuses dotfiles.
  • SEC-005: Sitemap reads enforce response, aggregate-byte, document, target-count, redirect and total deadline budgets. Compressed responses are decoded within byte/deadline limits; discarded redirect/error bodies are closed.
  • SEC-006: The repository's active main ruleset now requires PRs, resolved review threads and all ten existing GitHub Actions checks on an up-to-date branch. Sam selected zero mandatory approvals. Existing history protections remain, with no bypass actors. This setting is already applied and verified on GitHub independently of candidate publication.

Compatibility and configuration

The Node floor remains 22.12.0. Managed dependencies are Puppeteer 25.16.0, axe-core 4.12.1, Zod 4.6.7, follow-redirects 1.16.1 and fast-uri 3.1.9 in their respective lockfile graphs. The scanner manifest permits only the pinned Puppeteer lifecycle script under npm's explicit script policy.

Default execution policy is tighter than v3.2.0. Additional target/navigation origins require a reviewed --allow-origin list, the Action's allow-origin input, or the adapter's discovery.allowed_origins array. The legacy cross-origin sitemap-document option does not approve page origins. Explicit URL lists and preview-host rewriting remain supported.

An isolated incompatible runner can explicitly select --no-sandbox, Action no-sandbox: true, or adapter scan.no_sandbox: true. The default remains false and the override emits a warning. Repository Ubuntu fixture jobs opt in explicitly; local verification also exercises sandbox-enabled Chromium.

Direct sitemap limits are 2 MiB per response, 10 MiB total, 50 documents, 10,000 distinct targets, five redirects per document, and thirty seconds for the complete load. Discovery reads use the same bounded HTTP helper with a ten-second absolute deadline per resource. Read network and browser policy before migrating.

Review and verification

The release record owns current test results, source fingerprints, archive digests, independent review and the exact publication boundary. The remediation record maps each original finding to its proof and regression coverage.

Guide 0.3.18 binds the released executable bytes and local helper integrity checks. Root and hosted-copy source bytes are identical; the sidecar identifies the published release. The GuideCheck metadata vocabulary uses status: active, distinct from release publication status. The prior human last-reviewed date is preserved. Local verification does not establish hosted acceptance or independent release anchoring.

Residual scope

Approved origins and main-frame navigation restrictions are not a network sandbox for arbitrary page subresources, workers, popups, DNS rebinding or browser compromise. Use a suitable isolated runner/network for untrusted sites. Authenticated outputs can still contain sensitive page content despite supplied credential-value redaction. Project/global package fallbacks need separate dependency review.

Automated checks do not certify WCAG or legal conformance. Release assets are built from the approved release commit after exact-head CI. Pages waits for its release tag and named assets before deploying the guide.

Publication verification

PR 31 passed all ten checks at final head c269c4b; the release merge 6d153f9 passed all ten again. The signed tag is verified. Both221-file archives match every release Git blob, and all three public asset downloads match SHA256SUMS and GitHub asset digests.

The downloaded package passed Node 22.12.0 validation 32/32, CLI 17/17, eight sandbox-enabled security groups, browser/authentication, four external CLI consumers and site checks. All11 deployed public files match release-build bytes; the missing route returns 404. Hosted GuideCheck reports Level 4, zero blockers and one existing nosniff-header warning for guide 0.3.18 SHA256 8a8db727de9d89cb3734d6e21a9c7deab74eb5aa812a10fd05bd5e6462408512.

Detailed publication receipt · PR CI · Release-commit CI · Pages.

v3.2.0: Authenticated scan inputs

This release adds bounded authenticated scans to the existing Puppeteer engine. Supply Playwright-format cookies and local storage together with per-target expected URLs and visible readiness selectors. The scanner, JSON adapter and reusable Action accept the same paired inputs. Each target receives a fresh context, and authentication failures remain operational failures even when

... (truncated)

Changelog

Sourced from snapsynapse/skill-a11y-audit/.github/actions/scan's changelog.

v3.3.0: Security execution defaults

Security release, 2026-10-26. Published tag, asset and hosting evidence is maintained in the repository release record.

Security fixes

  • SEC-001: Dependency checks reject unavailable, malformed and inconsistent npm audit reports. Valid reports remain usable when npm's configured severity threshold produces exit 0 with nonblocking advisories.
  • SEC-002: Discovery excludes unapproved sitemap targets; direct sitemap scanning rejects unapproved leaves, child documents and redirects. Scanner top-level navigation and redirects are confined to approved origins. Plan metadata cannot grant new permission.
  • SEC-003: Chromium sandboxing is enabled by default. An explicit override is available for a separately isolated runner; there is no silent fallback.
  • SEC-004: The temporary Action server binds to loopback, disables directory listings and refuses dotfiles.
  • SEC-005: Sitemap reads enforce response, aggregate-byte, document, target-count, redirect and total deadline budgets. Compressed responses are decoded within byte/deadline limits; discarded redirect/error bodies are closed.
  • SEC-006: The repository's active main ruleset now requires PRs, resolved review threads and all ten existing GitHub Actions checks on an up-to-date branch. Sam selected zero mandatory approvals. Existing history protections remain, with no bypass actors. This setting is already applied and verified on GitHub independently of candidate publication.

Compatibility and configuration

The Node floor remains 22.12.0. Managed dependencies are Puppeteer 25.16.0, axe-core 4.12.1, Zod 4.6.7, follow-redirects 1.16.1 and fast-uri 3.1.9 in their respective lockfile graphs. The scanner manifest permits only the pinned Puppeteer lifecycle script under npm's explicit script policy.

Default execution policy is tighter than v3.2.0. Additional target/navigation origins require a reviewed --allow-origin list, the Action's allow-origin input, or the adapter's discovery.allowed_origins array. The legacy cross-origin sitemap-document option does not approve page origins. Explicit URL lists and preview-host rewriting remain supported.

An isolated incompatible runner can explicitly select --no-sandbox, Action no-sandbox: true, or adapter scan.no_sandbox: true. The default remains false and the override emits a warning. Repository Ubuntu fixture jobs opt in explicitly; local verification also exercises sandbox-enabled Chromium.

Direct sitemap limits are 2 MiB per response, 10 MiB total, 50 documents, 10,000 distinct targets, five redirects per document, and thirty seconds for the complete load. Discovery reads use the same bounded HTTP helper with a ten-second absolute deadline per resource. Read network and browser policy before migrating.

Review and verification

The release record owns current test results, source fingerprints, archive digests, independent review and the exact publication boundary. The remediation record maps each original finding to its proof and regression coverage.

Guide 0.3.18 binds the released executable bytes and local helper integrity checks. Root and hosted-copy source bytes are identical; the sidecar identifies the published release. The GuideCheck metadata vocabulary uses status: active, distinct from release publication status. The prior human last-reviewed date is preserved. Local verification does not establish hosted acceptance or independent release anchoring.

Residual scope

Approved origins and main-frame navigation restrictions are not a network sandbox for arbitrary page subresources, workers, popups, DNS rebinding or browser compromise. Use a suitable isolated runner/network for untrusted sites. Authenticated outputs can still contain sensitive page content despite supplied credential-value redaction. Project/global package fallbacks need separate dependency review.

Automated checks do not certify WCAG or legal conformance. Release assets are built from the approved release commit after exact-head CI. Pages waits for its release tag and named assets before deploying the guide.

Commits
  • 6d153f9 Merge pull request #31 from snapsynapse/codex/security-hardening-3.3.0
  • c269c4b fix: report Pages release wait progress
  • 3e3dbe9 fix: harden scan execution for v3.3.0
  • 2c21b9a Merge pull request #30 from snapsynapse/dependabot/npm_and_yarn/a11y-audit/de...
  • 1d2c43f docs: retain full security audit and reproducible evidence
  • fb72bbe fix: synchronize dependency security updates and validation
  • d07481e Merge remote-tracking branch 'origin/dependabot/github_actions/astral-sh/setu...
  • e762be9 Merge remote-tracking branch 'origin/dependabot/npm_and_yarn/fast-uri-3.1.9' ...
  • 7f06703 Merge remote-tracking branch 'origin/dependabot/npm_and_yarn/a11y-audit/deps/...
  • 04b8a83 build(deps): bump zod and puppeteer in /a11y-audit/deps
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [snapsynapse/skill-a11y-audit/.github/actions/scan](https://github.com/snapsynapse/skill-a11y-audit) from 2.7.0 to 3.3.0.
- [Release notes](https://github.com/snapsynapse/skill-a11y-audit/releases)
- [Changelog](https://github.com/snapsynapse/skill-a11y-audit/blob/main/RELEASE_NOTES-3.3.0.md)
- [Commits](snapsynapse/skill-a11y-audit@88b5561...6d153f9)

---
updated-dependencies:
- dependency-name: snapsynapse/skill-a11y-audit/.github/actions/scan
  dependency-version: 3.3.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 1, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants