blitzstrike 2.4.140 → 2.4.141
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 +9 -2
- package/package.json +1 -1
- package/skills/hp-full-security-audit.md +0 -8
package/CHANGELOG.md
CHANGED
|
@@ -5,9 +5,16 @@ All notable changes to Blitz Strike are documented here.
|
|
|
5
5
|
The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/).
|
|
7
7
|
|
|
8
|
+
## [2.4.141] — 2026-10-02
|
|
9
|
+
|
|
10
|
+
### Changed — removed third-party tool references from public artifacts
|
|
11
|
+
|
|
12
|
+
- Stripped competitor tool/brand references from the source, CHANGELOG, and skill
|
|
13
|
+
files so Blitz Strike's public surface is self-contained.
|
|
14
|
+
|
|
8
15
|
## [2.4.140] — 2026-10-02
|
|
9
16
|
|
|
10
|
-
### Added — severity ≤ evidence ceiling
|
|
17
|
+
### Added — severity ≤ evidence ceiling
|
|
11
18
|
|
|
12
19
|
- `severity_calibrate` now takes an `evidence_level` (declared | resolved |
|
|
13
20
|
call_path | runtime) that CAPS the reportable severity + priority: declared ≤
|
|
@@ -65,7 +72,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
|
|
|
65
72
|
|
|
66
73
|
## [2.4.135] — 2026-10-02
|
|
67
74
|
|
|
68
|
-
### Added — triage-honesty doctrine + submission floors
|
|
75
|
+
### Added — triage-honesty doctrine + submission floors
|
|
69
76
|
|
|
70
77
|
- submission_gate now asks 9 questions (was 7): + impact_demonstrated (the actual
|
|
71
78
|
attacker outcome / credential authority was probed, not just "the mechanism
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "blitzstrike",
|
|
3
|
-
"version": "2.4.
|
|
3
|
+
"version": "2.4.141",
|
|
4
4
|
"description": "Blitz Strike — a universal MCP security-audit toolbelt. BLITZ sweeps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE verifies live. 57 attack chains, 130-tool catalog, intelligence data layer. One server, every agent.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -49,14 +49,6 @@ In this order, since each informs the next:
|
|
|
49
49
|
|
|
50
50
|
[`findings-report`](../findings-report/SKILL.md) — synthesize everything under `findings/` into one ranked report using `templates/finding-report.md`. This is the actual deliverable; nothing before this step should be shown to the user as a final answer on its own.
|
|
51
51
|
|
|
52
|
-
## Optional — agentic deep pass
|
|
53
|
-
|
|
54
|
-
For a target that warrants it (pre-launch, handling real user funds/data, or just wanting a second independent pass), [strix](https://github.com/usestrix/strix) is a good complement: an autonomous AI pentesting agent that runs its own recon→exploit→validate loop and produces working PoCs. Not a replacement for the structured pass above, but a useful "have a second, differently-built system try to break it" layer:
|
|
55
|
-
|
|
56
|
-
```bash
|
|
57
|
-
strix --target <path-or-url>
|
|
58
|
-
```
|
|
59
|
-
|
|
60
52
|
## Notes for whichever agent is running this
|
|
61
53
|
|
|
62
54
|
- Don't run every skill blindly — think about what actually applies, same as a human pentester would scope an engagement before starting.
|