Stage-1 SAFE runs on a session whose shell moved PATH
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bash, typescript
Research direction
Start with index.ts, especially the stage-1 SAFE branch and the stage-2 stageTwo latch, then read docs/plans/2026-11-04-stage-2-latch-scope.md. Determine how the host reports shell-state drift and how often sessions drift before deciding how the new refusal should apply. Done means a SAFE bare-name command in a drifted session is blocked consistently with a reviewer allow, with the drift measurement informing the added refusals.
Written by the indexing model from the issue text.
Description
A stage-1 SAFE auto-runs on a session whose shell an earlier call changed. https://github.com/STRML/omp-classifier/pull/225 only stops the stage 2 reviewer once a session moves PATH, adds an alias or defines a function. Jev's own SAFE never checks.
call 1: export PATH=$PWD/.bin:$PATH (gate judges it, runs)
call 2: git status Jev SAFE ─▶ runs .bin/git
| Path | Checks shell state? |
|---|---|
stage 1 SAFE, branch 3 (index.ts if (judgement.verdict === "SAFE")) |
no |
| stage 2 reviewer allow | yes (latch, index.ts stageTwo) |
The latch covers the weaker path only. Jev reads the command text, and git status is SAFE text whatever git resolves to.
The fix rides on the shell-state check planned in docs/plans/2026-11-04-stage-2-latch-scope.md: once the host reports drift against the session's baseline, a SAFE on a bare name in a drifted session should block the same way a reviewer allow does. That adds refusals, so it wants a measurement of how often sessions drift first.
Found by the auditor seat during plan review for the latch fix.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 82
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from STRML/omp-classifier
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
STRML/omp-classifier#259 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
STRML/omp-classifier#256 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
STRML/omp-classifier#252 ·
Maintainers usually reply within 1 day
All issues in STRML/omp-classifier
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/langchainjs#12239 ·
Maintainers usually reply within 1 day
-
Board view: the Monitoring column is always empty because compact issue rows drop displayStatusOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
paperclipai/paperclip#21837 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
code-yeongyu/senpi#6813 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 93/100
lingdojo/kana-dojo#34169 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100