Compétences safe-refactor Historique des audits
📦

Historique des audits

safe-refactor - 2 audits

Comparaison des versions

Évolution des capacités et des constats entre les versions auditées, les plus récentes en premier.

VersionDateRésultatÉléments à examinerChangement vs précédente
v2 Dernier22 oct. 2026, 19:27 Aucun constat confirmé0Aucun changement de capacité
v1 17 oct. 2026, 19:54 1 confirmé0Référence

22 oct. 2026, 19:27

All three static findings are false positives: Markdown command references are not Ruby execution, and the completion report is not system reconnaissance. No evidence found of prompt injection, data exfiltration, or malicious intent in SKILL.md.

1
Fichiers analysés
38
Lignes analysées
1
Éléments à examiner
0
Faux positifs ignorés

Facteurs de risque

⚙️ Commandes externes (2)
Audité par: codex

17 oct. 2026, 19:54

All three static findings are false positives: inline Markdown command references and a completion report do not establish shell execution or system reconnaissance. A separate rollback instruction could discard pre-existing user edits if git restore is applied without isolating the refactoring changes. No evidence found of prompt injection, credential access, or data exfiltration.

1
Fichiers analysés
38
Lignes analysées
2
Éléments à examiner
0
Faux positifs ignorés

Préoccupations de sécurité confirmées (1)

Moyen
Rollback Guidance May Discard Existing Changes
The instruction says to undo a failed step using git restore without requiring preservation of existing edits. Restoring an entire modified file could discard unrelated user work.
The rollback instruction names git restore without a change-ownership safeguard. Data loss depends on the selected paths or hunks and pre-existing edits.

Facteurs de risque

⚙️ Commandes externes (2)
Audité par: codex