Add security scan receipt metadata#1405
Closed
HarperZ9 wants to merge 1 commit into
Closed
Conversation
Author
|
Closing this as a duplicate of #1404. I opened this after working from #1273, but #1404 was already open and is the stronger consolidation point: it adds the componentized receipt schema, official-registry behavior notes, generated schema output, and full local validation from the repo toolchain. Keeping both open would split maintainer review for the same v1 shape. I'll route any further review comments to #1404. |
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.
Refs #1273.
Summary
_meta[io.modelcontextprotocol.registry/security-scan]receipt metadata toServerDetail.server.schema.jsonfrom the OpenAPI source.cleanis scoped to the artifact, scanner, rule set, policy profile, andscanScope; it is not a global server-safety claim.I used camelCase for receipt fields to match the existing
server.jsonschema conventions. The inconclusive reason values remain machine-readable enum strings.Verification
openapi.yamlparses with PyYAML.server.schema.jsonpasses Draft 7 schema validation with Pythonjsonschema.security-scanreceipt example validates against the draft schema.tools/extract-server-schemaproduced a byte-identicalserver.schema.jsonafter Go-style JSON escaping.git diff --checkpassed.Local note: this Windows shell does not have
makeorgo, so I could not runmake generate-schemaormake check-schemadirectly. The generated schema parity check above follows the repository extraction logic and verifies the checked-in draft schema is synchronized withopenapi.yaml.