nsauditor-ai 0.2.33 → 0.2.34

package/README.md

@@ -17,6 +17,8 @@ NSAuditor AI is the open-source core of a privacy-first security intelligence pl
 
 ## What's New
 
+**Internal-provenance strip + a false-clean closure (CE 0.2.34 / Enterprise 0.32.9).** Paired with Enterprise 0.32.9. The evidence pack a customer hands their auditor no longer carries internal engineering markers — **686 unexplained occurrences → 0** on a rebuilt three-cloud pack, with a positive control so the zero is a measurement rather than an absence of looking. Two behavioural fixes ride with it: a cloud plugin that returns `up:false` (optional SDK absent, credentials unusable) now fail-closes an evidence gap on every in-scope control of that cloud instead of leaving them PASS, and an archived scan conclusion re-mapped through the new build warns instead of failing clean. CE's side: the MCP `scan_cloud` summary strips **both** spellings of the evidence-gap routing prefix, so an operator pairing this CE with an older Enterprise still gets a clean one-line summary. **⚠️ If you suppress by `titlePattern` on the old violation text, re-point it — see the [Enterprise CHANGELOG](https://github.com/nsasoft/nsauditor-ai-ee/blob/main/CHANGELOG.md).**
+
 **Capability-claim honesty pass, part 2 — the air-gapped-delivery class (CE 0.2.33 / Enterprise 0.32.8).** Paired with Enterprise 0.32.8, a **documentation-and-prose release** — no detection, routing, or compliance behaviour changes. 0.32.7 withdrew six phantom capability *flags*; an audit of the air-gapped-delivery claims found the same class one layer down, in prose, across **27 sites** (distinct lines) in the three published packages. **CE fix this cycle — `--out` with a version-named directory.** `--out .../ee-0.32.8` silently wrote artifacts to the *parent* directory: the file-vs-directory check keyed on "has an extension", and `path.parse('ee-0.32.8').ext` is `'.8'`. The same shape broke `v1.2.3` and `release-2026.07`. An extension now counts as file-like only if it starts with a letter, so version-named output directories work and `--out report.json` still resolves to its parent. Found by the pre-publish smoke gate running the documented command end-to-end. **CE docs change this cycle:** the ZDE section's *"Fully air-gappable. Every feature works without internet access"* is corrected to **"Air-gappable, once configured for it"** — scanning, analysis, license verification and evidence-pack generation all run with no outbound network access, and Enterprise adds offline CVE matching under `NSAUDITOR_OFFLINE_ONLY=1` (which emits an explicit coverage gap rather than a silent clean when the local store cannot answer), but a **default** scan still attempts NVD egress unless that variable is set, and the only other outbound paths — AI enrichment and the GRC push — are opt-in and off by default. The claim that Enterprise "includes offline NVD feeds" is **WITHDRAWN**: no feed data is delivered with the product, and populating the local store is the operator's. Held by a new mutation-proven guard (`tests/capability_claim_honesty.test.mjs`) that fails the build both if the absolute claim returns **and** if the honest qualifier is deleted. On the Enterprise side the same sweep found **five** rendered runtime strings — prose that reaches the assessor-facing evidence pack — making claims the code does not support. Plugin count UNCHANGED at 28; all seven coverage matrices UNCHANGED. See **[CHANGELOG.md](./CHANGELOG.md)** for the full per-release history.
 
 **Cross-framework routing + capability-claim honesty pass (CE 0.2.32 / Enterprise 0.32.7).** Paired with Enterprise 0.32.7, a **matrix-neutral** release. The network-scan analysis agents' findings now route in **all seven compliance frameworks** — a host serving cleartext or exposing SMB previously failed the SOC 2 report and read clean in HIPAA / NIST CSF / ISO 27001 / CIS v8 / PCI / GDPR off the *same scan*; that gap is closed (48 mapping rules across the seven framework files, a mutation-proven drift guard, all coverage matrices byte-identical). And a **capability-claim honesty pass** withdraws several Pro/Enterprise capabilities that were advertised without a shipping implementation. **CE code change this cycle:** the tier-capability map (`utils/capabilities.mjs`) drops six flags — `verificationEngine`, `brandedReports`, `usageMetering`, `dockerIsolation` (no implementation) and `zdePolicyEngine`, `enterpriseCTEM` (real cores ship + are claimed in prose; no distinct engine behind the name) — in lockstep with Enterprise and both licensing repos, so `nsauditor-ai license --capabilities` and every minted license now name only capabilities that ship. `resolveCapabilities(tier)` derives from tier and ignores the JWT capability array, so **issued licenses are unaffected**. Plugin count UNCHANGED at 28; all seven coverage matrices UNCHANGED. See **[CHANGELOG.md](./CHANGELOG.md)** for the full per-release history.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nsauditor-ai",
-  "version": "0.2.33",
+  "version": "0.2.34",
   "description": "Modular AI-assisted network security audit platform — Community Edition",
   "type": "module",
   "private": false,

package/utils/cloud_finding_summary.mjs

@@ -26,11 +26,19 @@ export const GAP_CLAUSE_RE =
 // Substrate-evidence PASS prose (1220/1222 push these into the same issues[] as
 // violations) — informational; never a lead clause while any alternative exists.
 const PASS_CLAUSE_RE = /substrate evidence:/i;
-// EE compliance-routing tag (e.g. 'EE-RT.1.2 multi-region-enumeration-incomplete: ')
-// leading many gap emissions — anchor plumbing for the EE framework JSONs, not
-// operator prose. Stripped at THIS presentation layer only (routing matches the
-// RAW issue strings EE-side) so the 160-char slice spends its budget on substance.
-const ROUTING_PREFIX_RE = /^EE-RT\.[\dx.]+ [a-z][a-z-]*: /;
+// EE compliance-routing tag leading many gap emissions — anchor plumbing for the EE
+// framework JSONs, not operator prose. Stripped at THIS presentation layer only (routing
+// matches the RAW issue strings EE-side) so the 160-char slice spends its budget on
+// substance; the [⚠ EVIDENCE GAP] badge already says it is a gap.
+//
+// TWO SPELLINGS, and the old one must stay. EE renamed the prefix in its A1 cycle ③ —
+// `EE-RT.1.2 multi-region-enumeration-incomplete: ` became
+// `Evidence gap (multi-region enumeration incomplete): ` — because it renders as the
+// violation TITLE in the customer's evidence pack and an internal roadmap id has no
+// business there. CE ships independently of EE and an operator can pair ANY supported EE
+// with this CE, so dropping the old alternative would leave the old prefix unstripped on
+// every paired-with-older-EE run. Recognise both.
+const ROUTING_PREFIX_RE = /^(?:EE-RT\.[\dx.]+ [a-z][a-z-]*|Evidence gap \((?:scan time budget exceeded|multi-region enumeration incomplete)\)): /;
 
 function classifyClause(s) {
   if (PASS_CLAUSE_RE.test(s)) return 'pass';

package/utils/validate.mjs

@@ -57,11 +57,33 @@ export async function checkPlugins({ discover, pkgRoot = PKG_ROOT } = {}) {
     const fn = discover || (await import('./plugin_discovery.mjs')).discoverPlugins;
     const result = await fn(pkgRoot);
     const plugins = Array.isArray(result) ? result : (result?.plugins ?? []);
+    // `discoverPlugins` reads THREE sources: CE plugins under `pkgRoot`, the EE package
+    // resolved GLOBALLY (it is a separate npm package, so `pkgRoot` cannot and should not
+    // reach it), and NSAUDITOR_PLUGIN_PATH. Reporting the aggregate count beside a single
+    // `basePath` produced "28 plugins loaded / basePath: <dir>" for a directory containing
+    // NONE of them — a false report from the command an operator runs to check their install.
+    // Each plugin already carries `_source`; use it, so `basePath` describes what it counts.
+    const bySource = {};
+    for (const p of plugins) bySource[p?._source ?? 'unknown'] = (bySource[p?._source ?? 'unknown'] ?? 0) + 1;
+    const ceCount = bySource.ce ?? 0;
+    const others = Object.entries(bySource).filter(([k]) => k !== 'ce');
+    // Only claim attribution we actually have. An injected `discover` (tests, embedders) may
+    // return plugins without `_source`; asserting "0 at basePath" there would be a different
+    // false report from the one this fix removes.
+    const attributable = Object.keys(bySource).some((k) => k !== 'unknown');
+    const suffix = others.length ? ` (+ ${others.map(([k, n]) => `${n} ${k}`).join(', ')})` : '';
     return {
       name: 'plugins',
       status: STATUSES.OK,
-      message: `${plugins.length} plugin${plugins.length === 1 ? '' : 's'} loaded`,
-      details: { count: plugins.length, basePath: pkgRoot },
+      message: attributable
+        ? `${ceCount} plugin${ceCount === 1 ? '' : 's'} at basePath${suffix}`
+        : `${plugins.length} plugin${plugins.length === 1 ? '' : 's'} loaded`,
+      details: {
+        count: plugins.length,
+        basePathCount: attributable ? ceCount : plugins.length,
+        bySource,
+        basePath: pkgRoot,
+      },
     };
   } catch (err) {
     return {