Skip to content

fix: retain JSON grammar for decoded signing bundles - #1038

Draft
yashrajp22 wants to merge 13 commits into
mainfrom
yashraj/oms-projected-json-context
Draft

yashrajp22 wants to merge 13 commits into
mainfrom
yashraj/oms-projected-json-context

Conversation

@yashrajp22

Copy link
Copy Markdown
Collaborator

Decoded signing bundles are canonical JSON, but their carrier filenames can select shell-like or Python string handling. Literal backticks and quotes in readable certificate or payload fields can then produce an incorrect parser limitation.

Use JSON grammar for parser-boundary checks on decoded bundle views while preserving the original carrier path, evidence, security rule applicability, and resource bounds. Unrecognized or malformed bundles retain their existing incomplete-analysis behavior. This composes with the marker ownership changes in #1033.

@yashrajp22 yashrajp22 closed this Nov 5, 2026
@yashrajp22 yashrajp22 reopened this Nov 5, 2026
@yashrajp22 yashrajp22 closed this Nov 6, 2026
@yashrajp22 yashrajp22 reopened this Nov 6, 2026
@yashrajp22 yashrajp22 closed this Nov 6, 2026
@yashrajp22 yashrajp22 reopened this Nov 6, 2026
@yashrajp22 yashrajp22 closed this Nov 6, 2026
@yashrajp22 yashrajp22 reopened this Nov 6, 2026
@yashrajp22 yashrajp22 closed this Nov 6, 2026
@yashrajp22 yashrajp22 reopened this Nov 6, 2026
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