@clear-capabilities/agentic-security-scanner 0.124.0 → 0.124.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,18 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.124.1 — fix: narration no longer prints a broken location
|
|
4
|
+
|
|
5
|
+
Now that v0.124.0 surfaces `narration` prominently inline, a pre-existing template
|
|
6
|
+
bug became visible: some narrations read `app.js:?` / `app.js:undefined` because the
|
|
7
|
+
location was interpolated before the finding's line was finalised.
|
|
8
|
+
|
|
9
|
+
- `scanner/src/posture/flow-narration.js`: the location is redundant (the finding
|
|
10
|
+
header already shows `file:line`), so the family templates are now
|
|
11
|
+
location-agnostic, and `_routeOf()` (generic fallback + LLM prompt) falls back to
|
|
12
|
+
the file alone — or "this endpoint" — instead of emitting `:undefined` / `:?`.
|
|
13
|
+
- Regression test in `test/flow-narration.test.js` asserts no template renders a
|
|
14
|
+
broken location when the line is absent.
|
|
15
|
+
|
|
3
16
|
## 0.124.0 — inline finding depth (no second command for "why it fired")
|
|
4
17
|
|
|
5
18
|
The depth `/triage --explain` produces now renders **inline** in the finding views,
|