Repository navigation
Conversation
ottosulin
force-pushed
the
feat/aisvs-1.01
branch
from
November 14, 2026 18:53
9c12458 to
1d432df
Compare
Retargets the three AISVS mapping files to the frozen 1.01 release (October 2026): 213 registry controls, 328 mapping rows, and the schema v2 columns filled with Framework ver. pinned to AISVS 1.01. Signed-off-by: Otto Sulin <ottosulin@users.noreply.github.com>
ottosulin
force-pushed
the
feat/aisvs-1.01
branch
from
November 14, 2026 18:58
1d432df to
14d6b93
Compare
ottosulin
marked this pull request as ready for review
November 14, 2026 18:58
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR changes
Retargets the three AISVS mapping files from AISVS 1.0 to the frozen 1.01 release (October 2026).
data/framework-sources.json, and the framework name ingenerate.js,compliance-report.js,inventory-completeness.js,README.mdandCHANGELOG.mdFramework ver.pinned toAISVS 1.01Type of change
Source / evidence
Checklist
Content
Links & data
.mdlinks resolvelycheenot run; the 44 changed AISVS anchors and every registry URL were checked insteaddata/schema.jsoncompatible: no new entry type, not applicableProject hygiene
CHANGELOG.mdupdatedREADME.mdupdated (framework name and its three file rows; file count unchanged)node scripts/validate.jspasses: 0 errors, 92 warnings (same as baseline), 329 checks.npm run buildclean,node --test137/137For new mapping files only
Not applicable.
Notes for reviewers
10.2.6is retired in 1.01 with no successor, so its single row was dropped rather than retargeted onto a different control.11.1.6has no counterpart in the 41 entries and is recorded as a gap, not forced onto an adjacent risk.npm run inventory, part ofbuild:reports, rewritesinventory_completenessin six registries away from what the repo ships. Not part of this PR; possibly worth a separate look.Disclosure: AI was used to build this change. Every row has
reviewed_by: Otto Sulin, changes were reviewed by me to ensure accuracy.