Skip to content

docs: fix stale independent-crosswalk count in README (3 -> 8) - #200

Open
chaksaray wants to merge 1 commit into
developfrom
fix/readme-crosswalk-count
Open

docs: fix stale independent-crosswalk count in README (3 -> 8)#200
chaksaray wants to merge 1 commit into
developfrom
fix/readme-crosswalk-count

Conversation

@chaksaray

Copy link
Copy Markdown
Contributor

Found while writing the org profile README (aveproject/.github, now live at github.com/aveproject).

This repo's own README undercounted its independent crosswalks in two separate places:

  • The top Independent validation section said "Three independent tools, cfgaudit, Ramparts, and nova-proximity."
  • The Framework crosswalks table's "This scanner → Maps to AVE via" only listed SkillSpector and ClawScan.

Verified against the real crosswalks/ directory rather than trusting either existing claim: 8 real, populated *-to-ave.json crosswalk files exist — cfgaudit, ClawScan, nova-proximity, Ramparts, Semia, SkillSpector (NVIDIA), skill-security-scanner, and skillsentry. Each checked individually for a real source.tool/vendor field and a non-empty mappings array, not assumed from the file listing alone. Semia in particular is already complete (16 mappings) — nothing in the corpus suggested it was still "in progress."

Both counts ("Three independent tools" → eight, named; "3 independent crosswalks" → 8) fixed, plus the crosswalk table filled out to all 8. No other stale count found elsewhere in the file.

Found while writing the org profile README (aveproject/.github):
this repo's own README undercounted its independent crosswalks in
two places -- the top 'Independent validation' section named only
cfgaudit, Ramparts, and nova-proximity ('Three independent tools'),
and the Framework crosswalks table listed only SkillSpector and
ClawScan under 'This scanner -> Maps to AVE via'. Verified against
the real crosswalks/ directory: 8 real, populated *-to-ave.json
crosswalk files exist (cfgaudit, ClawScan, nova-proximity, Ramparts,
Semia, SkillSpector, skill-security-scanner, skillsentry), each
checked for a real source.tool/vendor and a non-empty mappings array,
not assumed from the file list alone. Semia in particular was already
complete (16 mappings), not 'in progress.'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant