open/ms-ai-architect
1
0
Fork 0
Code Issues Releases 1 Activity
ms-ai-architect/SECURITY.md
Kjell Tore Guttormsen 7655f1798e chore(ms-ai-architect): bump v1.18.0 — korrekthetsprogrammet gikk fra dormant mekanisme til utfoert maaling [skip-docs] 
170 commits siden v1.17.0 (2026-07-04): 73 feat, 45 fix, 45 docs, 5 chore,
1 test, 1 refactor. 363 filer endret (71 nye, 3 slettet), 218 av 389
reference-filer. Suite 728 -> 1097, validate-plugin 250 PASS / 0 FAIL.

Den baerende endringen: v1.17.0 la substratet (Spor 1), denne utgivelsen
kjoerte mekanismen. Hele korpus-doemmepasset R7.1-R7.5 er utfoert over alle
243 aldri-verifiserte reference-filer (3 960 claims, 14 pass born-verified
stemplet, 229 flagged, 984 flagg), og R11 flag->fiks er i eksekvering
(74 av 81 G7-entries lukket, formene #14-#37 ratifisert).

Sideloepende fant kryssmodell-reviewen 2026-07-09 den eneste feilen i
utgivelsen som var synlig for en bruker uten aa lese ledgeren: pluginen
lastet KB feil i INSTALLERT modus - 115 relative KB-stier i 26 commands
og 10 agenter resolverte kun i dev-modus (RX-P1/P2).

Filer: plugin.json 1.17.0 -> 1.18.0, README-badge + ny historikk-rad,
SECURITY.md "currently", CHANGELOG [1.18.0]-seksjon med [Unreleased]-
punktet flyttet inn. [Unreleased] beholdt tom.

Tagg, katalog-ref og push gjoeres av operatoeren med
catalog/scripts/release-plugin.mjs ms-ai-architect --create-tag --write
--commit --push.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-12 21:18:05 +02:00

1.1 KiB
Raw Permalink Blame History

Security policy

Reporting a vulnerability

Report privately to security@fromaitochitta.com - do not open a public issue. Canonical repository: https://git.fromaitochitta.com/open/ms-ai-architect

Please include the affected version or commit, a minimal reproduction, and the impact you see. We acknowledge every report within 5 working days, agree a fix and disclosure timeline with the reporter, and aim to disclose within 90 days of the initial report.

Response process

  1. Acknowledge within 5 working days.
  2. Triage and confirm severity within 10 working days.
  3. Develop and test a fix.
  4. Publish an advisory and credit the reporter unless they prefer to remain anonymous.

Supported versions

The latest tagged release (currently 1.18.0) is the only supported version. Security fixes land on main and are released as a new tag; we do not backport fixes to older releases. See CHANGELOG.md for the release history.

Advisories

We publish advisories for confirmed vulnerabilities once a fix is available, crediting the reporter unless they request anonymity.