blitzstrike 2.4.59 → 2.4.61
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 +26 -0
- package/dist/index.js +1600 -1294
- package/intelligence/cwe_map.json +5 -1
- package/intelligence/patterns.json +36 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,32 @@ 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.61] — 2026-09-14
|
|
9
|
+
|
|
10
|
+
### Added — Automated verification harness (`blitzstrike verify`)
|
|
11
|
+
|
|
12
|
+
- New `src/verify-harness.ts`: exercises every detector against a POSITIVE fixture
|
|
13
|
+
(must fire) + a NEGATIVE fixture (must stay silent) and reports TP/FP/FN per
|
|
14
|
+
detector. Turns "battle-tested" from a claim into a command anyone can run.
|
|
15
|
+
- New `blitzstrike verify` CLI command (exits non-zero on any FN/FP) + a
|
|
16
|
+
`run_verification` MCP tool — the reproducible, regression-grade proof that all
|
|
17
|
+
19 single-file detectors still pass after any change (cross-file priv_esc is
|
|
18
|
+
covered by the verification corpus + cross-file regression).
|
|
19
|
+
|
|
20
|
+
## [2.4.60] — 2026-09-14
|
|
21
|
+
|
|
22
|
+
### Added — Modern attack-surface detectors + verification corpus
|
|
23
|
+
|
|
24
|
+
- Four new detector classes (the "next-gen" 2026 surface beyond classic web):
|
|
25
|
+
`llm_injection` (request input reaches an LLM call — OWASP LLM01), `graphql_exposure`
|
|
26
|
+
(introspection/playground left on), `oauth_misconfig` (redirect_uri fed by request
|
|
27
|
+
input with no allowlist), and `grpc_reflection` (reflection enabled). Each carries
|
|
28
|
+
CWE mapping + empirical pattern grounding.
|
|
29
|
+
- New `bench/verification/` — an auditable verification corpus: every detector that
|
|
30
|
+
was verified against a real vulnerable target gets a writeup (detector → ground
|
|
31
|
+
truth → result → evidence). "Battle-tested" is now a claim with an audit trail,
|
|
32
|
+
not an assertion.
|
|
33
|
+
|
|
8
34
|
## [2.4.59] — 2026-09-14
|
|
9
35
|
|
|
10
36
|
### Added — Severity calibration + engagement scaffold + data health
|