PortunusMCP Sentinel v1.3.0

PortunusMCP Sentinel 1.3.0 adds explicit rules-only scanning and includes the accepted Phase 16–18 correctness and first-use changes.

pipx install portunusmcp-sentinel==1.3.0
sentinel scan . --rules-only

• Rules-only: Python and TypeScript deterministic scans bypass model clients, review cache, network calls, Docker, runtime configuration, and target execution. Select with --rules-only, SENTINEL_RULES_ONLY, or [scanner].rules_only; CLI overrides environment, which overrides project configuration. Existing scan and Action defaults remain unchanged.
• First use: scanning needs no initialization. Default sentinel init writes only permissions. Python runtime scaffolding moves to sentinel init --dynamic, followed by sentinel scan . --no-rules-only; upgrades preserve validated existing permissions. Dynamic scans need Docker and model review, which transmits bounded source context and incurs model cost. TypeScript remains static-only.
• Integrations: the Action adds an inheritable rules-only input and pins the 1.3.0 package. The existing pre-commit hook uses rules-only. Fork credential restrictions and SARIF upload policy are preserved. Installation, dependency auditing, and eligible Action uploads have separate network requirements.
• Static correctness: supported same-file helper flows and value-specific validation, authentication, integrity, and sanitizer checks prevent unrelated checks from exempting unsafe inputs.
• Runtime evidence: probes require valid baselines and observable security violations. Per-probe outcomes and confirmed effects survive review; incomplete analysis returns exit 3.

--allow-degraded remains a fallback policy and can still call the model; use --rules-only to disable review. Findings retain thresholds, inline suppression, and baselines. Completed scans exit 0 below the threshold or 1 for threshold findings; input errors exit 2 and incomplete analysis exits 3. Completion does not prove a target is secure.

Compatibility: native JSON is 1.5.0, with nullable finding/provenance reviews and a null GPT summary in rules-only reports. Consumers requiring review objects must update. SARIF remains 2.1.0 and now exports stage records; older SARIF without stages remains readable. Baseline-v2 retains supported migration from native 1.3/1.4 reports without inventing runtime proof. Stable rule IDs are preserved.

• Changelog
• Phase 18 verification
• PyPI
• Documentation

Release commit: c45e10cf878cfa0f926687f88a5679729ce9a19f.

Verification: all 44 release jobs passed, including TestPyPI promotion, PyPI hashes and attestations, Linux/macOS/Windows Python 3.10–3.13 public installs, installed-wheel Docker replay, and mandatory network-isolated rules-only scans. All 27 main CI jobs passed. No paid model calls were used.

The exact v1.3.0 Action proof and signed v1 alias proof passed with complete rules-only reports, null model review, zero findings, and validated SARIF upload. Both signed tags resolve to the release commit. The older demo control was corrected to consume its validated model value after the first proof exposed a low-severity candidate; the scanner package was unchanged. These checks establish release integration, not broad detection accuracy.

SHA-256:

e5c529967c58735303b3ab5d6a836607d85f5f078949587a1335c5d6544d6cbf  portunusmcp_sentinel-1.3.0-py3-none-any.whl
859022c18bfd62f19983f98a40ad7ddb6ee14b655462f7217d6defd4acfd9523  portunusmcp_sentinel-1.3.0.tar.gz