chore(deps): bump tar from 7.5.21 to 7.5.22 in the production group across 1 directory

[dependabot]

Bumps the production group with 1 update in the / directory: tar.

Updates tar from 7.5.21 to 7.5.22

Commits

• 2a22bfc 7.5.22
• df1cd8d Allow transform to be falsey
• See full diff in compare view

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed July 27, 2026, 8:15 PM ET / July 28, 2026, 00:15 UTC.

ClawSweeper review

What this changes

Updates the direct optional tar dependency from 7.5.21 to 7.5.22 and refreshes the matching pnpm lockfile resolution and integrity entries.

Merge readiness

⛔ Blocked until real behavior proof from a real setup is added - 3 items remain

Keep this PR open for normal dependency review. It is a current, narrow update to the optional TAR parser used by archive extraction; current main has not absorbed the proposed 7.5.22 pin, and the supplied CI is useful supplemental validation but not after-update runtime proof for this filesystem-security boundary.

Priority: P2
Reviewed head: 9bb59994fbe894d12aabf5868fd86dcf5281acd8

Review scores

Measure	Result	What it means
Overall readiness	🦪 silver shellfish (2/6)	The patch is focused and mechanically consistent, but missing real archive-path proof keeps merge readiness low for this security-sensitive optional dependency.
Proof confidence	🧂 unranked krab (1/6)	Needs real behavior proof before merge: The supplied CI checks are useful but no after-update live TAR extraction result, redacted runtime log, terminal transcript, recording, or artifact demonstrates the changed dependency in the real archive path. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Needs proof	Needs real behavior proof before merge: The supplied CI checks are useful but no after-update live TAR extraction result, redacted runtime log, terminal transcript, recording, or artifact demonstrates the changed dependency in the real archive path. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Evidence reviewed	4 items	PR diff: The branch changes only the production optional dependency declaration and its lockfile entries from tar 7.5.21 to 7.5.22; no application behavior or package source is otherwise modified. Security-sensitive call path: The archive subsystem dynamically imports tar for TAR extraction and combines it with entry preflight, private staging, and guarded destination merging, so parser changes warrant targeted runtime validation. Current validation state: The supplied PR context reports successful package-smoke and Node check jobs across macOS, Ubuntu, and Windows, but no attached live post-update TAR extraction transcript or artifact.
Findings	None	None.
Security	None	None.

How this fits together

The archive API accepts an archive path and extracts TAR or ZIP content into a caller-provided destination. TAR extraction loads the optional tar package, preflights entries, stages output privately, and then merges it through fs-safe's guarded filesystem boundary.

flowchart LR
  A[Caller archive path] --> B[Archive API]
  B --> C[Archive kind selection]
  C --> D[Optional TAR parser]
  D --> E[Entry safety preflight]
  E --> F[Private staging directory]
  F --> G[Guarded destination merge]

Loading

Before merge

• Resolve merge risk (P1) - tar parses attacker-controlled archive formats in an optional production path; a patch release can alter extraction edge-case behavior even though fs-safe retains its own preflight and staging checks.
• Resolve merge risk (P1) - The package pin changes for consumers who install optional dependencies, so maintainers need confidence that ordinary TAR extraction and rejected traversal/link cases still behave correctly on the updated parser.
• Complete next step (P2) - A maintainer should review the upstream patch release and provide or accept targeted archive-boundary runtime evidence; no mechanical source repair is identified.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Patch surface	2 files affected; 6 additions, 6 deletions	The change is limited to the declared optional dependency and its generated lockfile resolution, which keeps functional review focused on parser compatibility.
Completed checks	20 successful checks; 1 check in progress	The supplied checks cover package smoke and Node validation on macOS, Ubuntu, and Windows, but do not replace targeted runtime archive proof.

Merge-risk options

Maintainer options:

1. Capture archive-boundary proof before merge (recommended)
   Run the updated package against a normal TAR fixture and unsafe traversal or link fixtures, then attach a redacted terminal transcript or runtime log showing the expected success and rejection behavior.
2. Accept CI-only evidence
   Maintainers may merge based on the existing multi-platform checks while explicitly accepting that no direct post-update TAR extraction evidence is attached.

Technical review

Best possible solution:

Retain the narrow 7.5.22 dependency update after a maintainer captures redacted runtime evidence for a successful TAR extraction plus rejected unsafe-entry behavior, alongside the existing CI coverage.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this PR is a dependency maintenance change rather than a report of broken behavior. The relevant validation is a post-update extraction run covering both accepted and rejected TAR inputs.

Is this the best way to solve the issue?

Unclear: the mechanical dependency and lockfile update is appropriately narrow, but direct runtime evidence is still needed because tar participates in the archive security boundary.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 1db7c7fa4a1c.

Labels

Label changes:

• add rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• remove rating: 🧂 unranked krab: Current PR rating is rating: 🦪 silver shellfish, so this older rating label is no longer current.

Label justifications:

• P2: This is a bounded production dependency update in a security-sensitive archive path, with no demonstrated active regression.
• merge-risk: 🚨 compatibility: Consumers installing optional dependencies will receive a different TAR parser whose archive edge-case behavior must remain compatible with fs-safe's extraction contract.
• merge-risk: 🚨 security-boundary: The updated package is directly loaded to parse TAR archives, an attacker-controlled input boundary protected by fs-safe's archive safeguards.
• rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The supplied CI checks are useful but no after-update live TAR extraction result, redacted runtime log, terminal transcript, recording, or artifact demonstrates the changed dependency in the real archive path. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Evidence

What I checked:

• PR diff: The branch changes only the production optional dependency declaration and its lockfile entries from tar 7.5.21 to 7.5.22; no application behavior or package source is otherwise modified. (package.json:148, 9bb59994fbe8)
• Security-sensitive call path: The archive subsystem dynamically imports tar for TAR extraction and combines it with entry preflight, private staging, and guarded destination merging, so parser changes warrant targeted runtime validation. (src/archive.ts, 1db7c7fa4a1c)
• Current validation state: The supplied PR context reports successful package-smoke and Node check jobs across macOS, Ubuntu, and Windows, but no attached live post-update TAR extraction transcript or artifact. (9bb59994fbe8)
• Prior review continuity: The prior ClawSweeper cycle identified the same missing real-behavior evidence; the later head refresh did not provide a linked runtime proof artifact, and there are no unresolved code findings to re-raise. (3643e4e67f87)

Likely related people:

• fs-safe archive contributors: The relevant code is the current-main TAR extraction path, but the supplied context contains no usable blame or commit-author metadata for that path; route to the people who recently maintain src/archive.ts and its extraction tests. (role: current archive-area ownership is not attributable from the available review context; confidence: low; commits: 1db7c7fa4a1c; files: src/archive.ts, package.json)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Attach redacted terminal or runtime-log proof of a successful TAR extraction using 7.5.22.
• Include a rejected traversal or link-entry case to show the guarded extraction boundary remains intact.
• After adding proof, update the PR body for a fresh ClawSweeper review; if it does not trigger, ask a maintainer to comment @clawsweeper re-review.

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (1 earlier review cycle)

• reviewed 2026-07-27T17:29:46.058Z sha 3643e4e :: needs maintainer review before merge. :: none

[steipete]

Merged after dependency and archive-boundary verification.

Tested at exact head 9bb59994fbe894d12aabf5868fd86dcf5281acd8:

• pnpm install --frozen-lockfile
• pnpm exec vitest run test/archive-policy.test.ts test/archive.test.ts test/native-archive-equivalence.test.ts — 35 passed, 3 platform/native skips
• GitHub CI: full Node 22/24, native, package-smoke, coverage, benchmark, workflow-lint, CodeQL, clippy, and audit checks green
• Codex autoreview: clean, no accepted/actionable findings

Landed as 90091fdf7d2a7d374bdc5207fc9663cc675be0b5. The focused runtime proof covered accepted TAR reads/extraction policy and rejected archive-boundary behavior on macOS; the cross-platform CI matrix remained green.