You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i want to add a grype reader to the scanner imports, is that something you'd take from outside or do you keep the readers in house?
i read how trivy and armorcode land: one *-findings.ts normalizer, golden tests, a docs row, wired into the read, local and publish maps. grype's sca json keys on package, advisory and path, so it maps onto the existing evidence contract without a new shape
i can prove it offline like examples/normalized-import, a saved grype -o json report through preview then import, no credentials, so a reviewer runs the whole thing
just want a yes on the direction first, and whether you'd want it cloud-supported like trivy or local-only like crowdstrike to start
Yes, we’d welcome a contribution. A local reader for saved grype -o json output would be a good first PR. The offline example you proposed is exactly what would help with review. A small fixture that previews, imports, and comes back unchanged on a second import would cover the path end to end.
Cloud publication needs the destination to accept the provider too. Let’s keep that as a follow-up. Thanks for asking about scope first.
Activity
[-]grype scanner importer, wanted from outside?[/-][+]add a grype scanner importer?[/+]mldangelo-oai commentedon Nov 15, 2026
Yes, we’d welcome a contribution. A local reader for saved
grype -o jsonoutput would be a good first PR. The offline example you proposed is exactly what would help with review. A small fixture that previews, imports, and comes back unchanged on a second import would cover the path end to end.Cloud publication needs the destination to accept the provider too. Let’s keep that as a follow-up. Thanks for asking about scope first.
Nixxx19 commentedon Nov 15, 2026
sounds good, i'll open it
local reader for saved grype json first, cloud as the follow-up
the fixture runs the whole path offline: preview, import, then a second import that does nothing, so a reviewer just runs it