#200

Bump deepsec to 2.3.13

Opengithub-actions[bot]wants to merge intofrom

Increases the deepsec package version from 2.3.12 to 2.3.13. Merging this PR triggers the release workflow.

Activity

3
vercel[bot]6d ago

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated
deepsec-website ReadyPreview, v0Nov 6, 2026 5:10pm UTC
1 Skipped Deployment
ProjectDeploymentActionsUpdated
deepsec Ignoredv0Nov 6, 2026 5:10pm UTC
auto-maintain[bot]6d ago

🤖 auto-maintain review

Automated, advisory triage for @github-actions[bot]'s PR. Facts below are read from the GitHub API.

CheckResult
Author's merged PRs (this repo)3
Account established✅ (age 3021d · 0 followers · 0 public repos)
Commits signed/verified✅ 1/1

Review panel: 🟢 low highest severity

deepsec maintainer code review: 🟢 low

The version-only release bump is consistent with the existing package and release workflow.

General code review: 🟢 low

The version-only change is consistent with the repository's release workflow and introduces no actionable issues.

Scanner and matcher quality: 🟢 low

Only the deepsec package version changes from 2.3.12 to 2.3.13; scanner and matcher behavior is unaffected.

Sandbox and credential boundaries: 🟢 low

The diff is a single version bump in packages/deepsec/package.json (2.3.12 → 2.3.13) with no code, workflow, or dependency changes; the release workflow fires only on push to main and publishes via OIDC trusted publishing, so no sandbox, egress, or credential boundary is affected and no hardcoded version references go stale.

Durability and distributed state: 🟢 low

The version-only change introduces no durability or distributed-state issues.

Posted by auto-maintain. This automated code review is advisory; a human maintainer makes the call.