The organization's crypto posture across a scope of projects
OMB M-23-02’s federal PQC inventory is posed at exactly this altitude.
Org-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as GET /v1/scans/projects:posture narrows one.
Scope uses the SAME vocabulary projects:posture accepts — projects and include_archived — so the estate canvas narrows both reads with one control. Ids outside the caller’s organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403.
A SEPARATE endpoint from projects:posture, deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization’s crypto data rather than its project count.
Numbers here are the SUM of the per-project crypto rollups GET /v1/scans/projects/{projectId}/summary returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and crypto.projects carries the per-project values so a client can verify it by addition. See EstateCryptoAggregate for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition.
Requires scans:read — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no crypto_not_entitled code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today.
A trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.
GET
/
v1
/
crypto
/
posture
The organization's crypto posture across a scope of projects
An Earnie API key, sent as Authorization: Bearer sk_earnie_.... Create one under Settings > API keys. The key's scopes decide which operations it may call.
Comma-separated project ids to narrow the scope to. Omitted means every non-archived project in the organization. A value that is not a uuid is a 400; an id the caller cannot see is dropped.
A bulk import batch id. Narrows the scope to the projects that batch has created so far, resolved on the server so the request stays one id long however large the import. Cannot be combined with projects. A batch that does not exist in the caller's organization is a 404; a batch that has created no project yet answers an empty scope, never the whole organization.
The scope's crypto posture. Always 200 for an authorized caller — an unmeasured estate, an unentitled organization and a failed findings read all return this shape with crypto absent, never an error and never zeros.
Two halves answering two different questions. The scope counts — projects_in_scope, projects_scanned, projects_not_scanned — say how much of the estate the numbers cover and are ALWAYS present. crypto carries the numbers, and is ABSENT when no project in scope has been measured.
Coverage is reported as its own field rather than left to subtraction, because a reader who has to compute it will not. "1,240 quantum-vulnerable assets" stated over a fifth of the estate is a different sentence from the same number stated over all of it, and an estate surface that cannot say which one it is saying is worse than no surface. Two invariants hold: projects_scanned + projects_not_scanned == projects_in_scope, and when crypto is present, projects_scanned == len(crypto.projects).
A project is MEASURED when it has EVER completed a crypto scan stage on a completed scan, OR it still holds active crypto findings. Both halves are load-bearing: the stage alone loses a project whose findings outlived the scan that found them, and the findings alone report a project the scanner cleared as never scanned. An unmeasured project is counted in projects_not_scanned, is absent from crypto.projects, and contributes to NO total on this payload. It is never folded in as a zero — that coercion turns "unknown" into "verified safe", which on a governance surface is the single error this response exists to prevent.
THAT RULE IS DELIBERATELY WIDER THAN THE PROJECT CARD'S, and the two are not interchangeable. ProjectCryptoSummary.crypto is present when the POSTURE SOURCE SCAN ran crypto to completion, or the project holds active crypto findings. This endpoint asks instead whether ANY completed scan of the project ever completed a crypto stage, which is a strict superset. The divergence has exactly one shape: scan A completes with a completed crypto stage and zero findings; scan B completes later, without crypto, and becomes the posture source. That project's own page reads "Crypto not scanned", while here it is counted in projects_scanned, listed in crypto.projects with zeros, and counted in export_readiness.ready_projects.
The wider rule is the right one at this altitude: a project the scanner ran and cleared IS measured, and the estate is where calling it unmeasured most distorts the coverage answer. The crypto NUMBERS still agree with the project card — such a project contributes zeros to every count — so the divergence is in coverage accounting (projects_scanned, export_readiness.ready_projects), never in a crypto total. crypto.projects[].last_crypto_scan_at is what lets a reader see it: it dates the older crypto scan the project page no longer reports.
An organization without the crypto scanner receives exactly this response with crypto absent and every project counted in projects_not_scanned — byte-identical to an entitled organization that has never run a crypto scan, and reached through the same code path rather than through an entitlement branch. There is deliberately no 403 and no crypto-specific error code: a distinguishable refusal would advertise entitlement state on a read surface that carries none today.
Projects this request resolved: the caller's organization, narrowed by projects, by include_archived, and by any project binding on the principal. The denominator every other count here is read against.
In-scope projects that are MEASURED under the union above. Equals len(crypto.projects) whenever crypto is present, and 0 whenever it is absent.
A measured project with zero crypto findings is counted HERE and contributes real zeros to every total. "Scanned and clean" and "never scanned" stay distinguishable at estate altitude, which is exactly where conflating them does the most damage: a clean headline covering projects nobody ever looked at is the report a CISO would act on and should not.
In-scope projects that are NOT measured. Its own field rather than projects_in_scope − projects_scanned, because a client that has to derive coverage will render the total without it.
This is also where a failed read lands. When the crypto findings for this scope cannot be read, the response degrades to ABSENCE — crypto omitted, every project counted here — never to zeros and never to an empty estate. That deliberately makes an outage indistinguishable from an unscanned estate ON THE WIRE; the server's WARN log is where an operator learns which one it was. The alternative shapes are both worse: zeros would claim a clean estate the store never confirmed, and a 500 would take down a page whose other cards are fine.
The aggregate itself. OPTIONAL, and its presence is the not-measured discriminator, exactly as ProjectCryptoSummary.crypto is for one project: ABSENT means no project in scope has ever completed a crypto stage and none holds an active crypto finding (or the read failed); PRESENT with all-zero counts means the scanner ran across the measured projects and found nothing.
Clients must never read absence as "clean" nor zeros as "not scanned", and must never render a total from this object without also rendering projects_not_scanned beside it.
Show child attributes
{"docsConfig":{"theme":"mint","$schema":"https://mintlify.com/docs.json","name":"SCANOSS documentation","colors":{"primary":"#FF6A1A","light":"#FF6A1A","dark":"#FF6A1A"},"logo":{"light":"https://mintcdn.com/scanoss/9UP7eHL2Z_rQPx8l/scanoss-logo-horizontal-positive.svg?fit=max\u0026auto=format\u0026n=9UP7eHL2Z_rQPx8l\u0026q=85\u0026s=686c4487013423ef804e2e83983c76ef","dark":"https://mintcdn.com/scanoss/9UP7eHL2Z_rQPx8l/scanoss-logo-horizontal-negative.svg?fit=max\u0026auto=format\u0026n=9UP7eHL2Z_rQPx8l\u0026q=85\u0026s=03cf2002f3fff2726f8e9b19bb2781ec","href":"https://scanoss.com"},"favicon":"https://mintcdn.com/scanoss/SuvZQ2xWfRUv4OAb/scan-favicon.png?fit=max\u0026auto=format\u0026n=SuvZQ2xWfRUv4OAb\u0026q=85\u0026s=4f02839460dfdc66102d3b028b507df6","appearance":{"default":"system","strict":false},"footer":{"socials":{"x":"https://x.com/SCANOSS_","github":"https://github.com/scanoss","linkedin":"https://es.linkedin.com/company/scanoss"}},"seo":{"indexing":"all"},"fonts":{"heading":{"family":"Space Grotesk","weight":700,"format":"woff2"},"body":{"family":"Space Grotesk","format":"woff2"}},"integrations":{"ga4":{"measurementId":"G-NWY31TXG8Y"}},"banner":{"content":"**Earnie is here** — SCANOSS's major release for AI governance, cryptography, PQC readiness, and open source compliance. [Watch the release demo →](https://youtu.be/MKgIpH4bEQ4?si=wXECS3umWGx11mB7)","dismissible":true},"contextual":{"options":["copy","view","claude","chatgpt","cursor","vscode","mcp"],"display":"header"},"styling":{"latex":false},"navigation":{"pages":[]}},"deployment":{"deploymentMetadataValue":{"subdomain":"scanoss","hasAudioNarration":false,"actualSubdomain":"scanoss","customDomains":["docs.scanoss.com"],"gitSource":{"type":"github","owner":"scanoss","repo":"docs","deployBranch":"main","contentDirectory":"","isPrivate":true,"mountPath":"","label":""},"entitlements":{"AI_CHAT":{"status":"ENABLED"},"WEB_MCP":{"status":"ENABLED"},"NARRATION":{"status":"ENABLED"}},"buildId":"6af4de431c57d74f3a12ae72","clientVersion":"0.0.4111","searchFilterCounts":[{"language":"default","tag":"Earnie","count":163},{"language":"default","tag":"API Reference","count":137},{"language":"default","tag":"Guides","count":84},{"language":"default","tag":"Developer Tools","count":67},{"language":"default","tag":"API reference","count":48},{"language":"default","tag":"v3 endpoints","count":47},{"language":"default","tag":"Scans","count":44},{"language":"default","tag":"scans","count":44},{"language":"default","tag":"Policies","count":22},{"language":"default","tag":"Findings","count":21}]},"assistantConfig":{"enableStarterQuestions":true,"deflection":{"enabled":true,"email":"support@scanoss.com","showHelpButton":true}},"basePath":"","hasChatPermissions":true,"hasWebMcpPermissions":true,"toggles":[{"name":"kill-isr","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"custom-rbac-roles","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"agent-mintlify-slack","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"agent-integrations-settings","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"rbac-expansion","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automations-pr-grouping","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"custom-prefix","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"analytics-v7","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"user-flows-analytics","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"no-publish-flow","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-onboarding","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"llms-txt-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"snapshot-serving-live","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"stripTemperatureMiddleware","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"support-platform-pylon-zendesk","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"snapshot-serving","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"instant-rollback","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"granular-notifications-server","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"granular-notifications","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automations-fable","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"fixed-ai-action-pricing","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automation-resolve-merge-conflict","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"scoped-publishing","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"mintql","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"page-level-analytics","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"editor-version-history-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"billing-page-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"full-page-search","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workspace-projects","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"assistant-v5","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"fork-pr-previews","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"revalidation-jwt","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-sso-scim","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"hobby-abuse-scan","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"dashboard-inbox","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-signup","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"turbopuffer-dual-write","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-enabled","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"approve-review-flow","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"editor-metadata","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"sso-setup-deadline-banner","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"turbopuffer-serve","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"live-agents","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false}],"starterQuestions":[{"_id":"695fa5b6a879c7d6b0e8a169","deploymentId":"68551e34bde804c6773f4df2","questionText":"Cannot import/export projects?","status":"active","generatedBy":"manual","createdAt":"2026-01-08T12:40:22.697Z","updatedAt":"2026-01-08T12:40:22.697Z","__v":0},{"_id":"695fa5a4a879c7d6b0e8a064","deploymentId":"68551e34bde804c6773f4df2","questionText":"Dependency files not detected during scan?","status":"active","generatedBy":"manual","createdAt":"2026-01-08T12:40:04.675Z","updatedAt":"2026-01-08T12:40:04.675Z","__v":0},{"_id":"695fa566a879c7d6b0e89d1e","deploymentId":"68551e34bde804c6773f4df2","questionText":"How do I configure the SCANOSS API key?","status":"active","generatedBy":"manual","createdAt":"2026-01-08T12:39:02.662Z","updatedAt":"2026-01-08T12:39:02.662Z","__v":0}],"googleFontsInlined":true},"customCss":[{"filePath":"style.css","content":"#banner{background-color:#ff6a1a!important;color:#ffffff!important}html:not(.dark) #background-color,html:not(.dark) #navbar-transition{background-color:#f4f6f9!important}html:not(.dark) h1{color:#081320!important}html:not(.dark) nav a[aria-current=\"page\"]{background-color:rgba(8, 19, 32, 0.1)!important}html:not(.dark) .chat-assistant-floating-input .bg-background-light,html:not(.dark) .chat-assistant-floating-input::before,html:not(.dark) #assistant-entry,html:not(.dark) #chat-assistant-sheet,html:not(.dark) #chat-assistant-sheet .bg-background-light{background-color:#f4f6f9!important}html.dark #background-color,html.dark #navbar-transition{background-color:#081320!important}html.dark h1,html.dark .prose :where(h1,h2,h3,h4,h5,h6),html.dark .prose :where(p,li,td,th):not(svg *){color:#ffffff!important}html.dark nav a[aria-current=\"page\"]{background-color:rgba(255, 106, 26, 0.15)!important}html.dark .chat-assistant-floating-input .dark\\:bg-background-dark,html.dark .chat-assistant-floating-input::before,html.dark #assistant-entry,html.dark #chat-assistant-sheet,html.dark #chat-assistant-sheet .dark\\:bg-background-dark{background-color:#081320!important}span[style*=\"radial-gradient\"]{display:none!important}nav#sidebar .sticky.top-0.h-8{display:none!important}#sidebar #navigation-items{padding-top:2rem}.eyebrow{color:#ff6a1a!important}nav a.text-primary{color:#ff6a1a!important}"}],"page":{"pagePath":"earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects","slug":"/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects","pageMetadata":{"title":"The organization's crypto posture across a scope of projects","description":"OMB M-23-02's federal PQC inventory is posed at exactly this altitude.\n\nOrg-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as `GET /v1/scans/projects:posture` narrows one.\n\nScope uses the SAME vocabulary `projects:posture` accepts — `projects` and `include_archived` — so the estate canvas narrows both reads with one control. Ids outside the caller's organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403.\n\nA SEPARATE endpoint from `projects:posture`, deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization's crypto data rather than its project count.\n\nNumbers here are the SUM of the per-project crypto rollups `GET /v1/scans/projects/{projectId}/summary` returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and `crypto.projects` carries the per-project values so a client can verify it by addition. See `EstateCryptoAggregate` for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition.\n\nRequires `scans:read` — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no `crypto_not_entitled` code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today.\n\nA trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/crypto/posture","href":"/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects","autogeneratedByOpenApi":true},"description":{"compiledSource":"\"use strict\";\nconst {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];\nconst {useMDXComponents: _provideComponents} = arguments[0];\nfunction _createMdxContent(props) {\n const _components = {\n code: \"code\",\n p: \"p\",\n ..._provideComponents(),\n ...props.components\n };\n return _jsxs(_Fragment, {\n children: [_jsx(_components.p, {\n children: \"OMB M-23-02’s federal PQC inventory is posed at exactly this altitude.\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"Org-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as \", _jsx(_components.code, {\n children: \"GET /v1/scans/projects:posture\"\n }), \" narrows one.\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"Scope uses the SAME vocabulary \", _jsx(_components.code, {\n children: \"projects:posture\"\n }), \" accepts — \", _jsx(_components.code, {\n children: \"projects\"\n }), \" and \", _jsx(_components.code, {\n children: \"include_archived\"\n }), \" — so the estate canvas narrows both reads with one control. Ids outside the caller’s organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403.\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"A SEPARATE endpoint from \", _jsx(_components.code, {\n children: \"projects:posture\"\n }), \", deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization’s crypto data rather than its project count.\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"Numbers here are the SUM of the per-project crypto rollups \", _jsx(_components.code, {\n children: \"GET /v1/scans/projects/{projectId}/summary\"\n }), \" returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and \", _jsx(_components.code, {\n children: \"crypto.projects\"\n }), \" carries the per-project values so a client can verify it by addition. See \", _jsx(_components.code, {\n children: \"EstateCryptoAggregate\"\n }), \" for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition.\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"Requires \", _jsx(_components.code, {\n children: \"scans:read\"\n }), \" — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no \", _jsx(_components.code, {\n children: \"crypto_not_entitled\"\n }), \" code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today.\"]\n }), \"\\n\", _jsx(_components.p, {\n children: \"A trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.\"\n })]\n });\n}\nfunction MDXContent(props = {}) {\n const {wrapper: MDXLayout} = {\n ..._provideComponents(),\n ...props.components\n };\n return MDXLayout ? _jsx(MDXLayout, {\n ...props,\n children: _jsx(_createMdxContent, {\n ...props\n })\n }) : _createMdxContent(props);\n}\nreturn {\n default: MDXContent\n};\n","frontmatter":{},"scope":{}},"pageType":"default","mdx":{"mdxSource":{"compiledSource":"\"use strict\";const{Fragment:_Fragment,jsx:_jsx}=arguments[0];const{useMDXComponents:_provideComponents}=arguments[0];function _createMdxContent(props){return _jsx(_Fragment,{})}function MDXContent(props={}){const{wrapper:MDXLayout}={..._provideComponents(),...props.components};return MDXLayout?_jsx(MDXLayout,{...props,children:_jsx(_createMdxContent,{...props})}):_createMdxContent(props)}return{default:MDXContent}","frontmatter":{},"scope":{"config":{},"pageMetadata":{"title":"The organization's crypto posture across a scope of projects","description":"OMB M-23-02's federal PQC inventory is posed at exactly this altitude.\n\nOrg-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as `GET /v1/scans/projects:posture` narrows one.\n\nScope uses the SAME vocabulary `projects:posture` accepts — `projects` and `include_archived` — so the estate canvas narrows both reads with one control. Ids outside the caller's organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403.\n\nA SEPARATE endpoint from `projects:posture`, deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization's crypto data rather than its project count.\n\nNumbers here are the SUM of the per-project crypto rollups `GET /v1/scans/projects/{projectId}/summary` returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and `crypto.projects` carries the per-project values so a client can verify it by addition. See `EstateCryptoAggregate` for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition.\n\nRequires `scans:read` — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no `crypto_not_entitled` code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today.\n\nA trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/crypto/posture","href":"/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects","autogeneratedByOpenApi":true}}},"mdxSourceWithNoJs":null},"mdxExtracts":{"tableOfContents":[],"codeExamples":{}},"jsLinks":[],"openApiReferenceData":{"operation":{"operationId":"GetV1CryptoPosture","summary":"The organization's crypto posture across a scope of projects","description":"OMB M-23-02's federal PQC inventory is posed at exactly this altitude.\n\nOrg-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as `GET /v1/scans/projects:posture` narrows one.\n\nScope uses the SAME vocabulary `projects:posture` accepts — `projects` and `include_archived` — so the estate canvas narrows both reads with one control. Ids outside the caller's organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403.\n\nA SEPARATE endpoint from `projects:posture`, deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization's crypto data rather than its project count.\n\nNumbers here are the SUM of the per-project crypto rollups `GET /v1/scans/projects/{projectId}/summary` returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and `crypto.projects` carries the per-project values so a client can verify it by addition. See `EstateCryptoAggregate` for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition.\n\nRequires `scans:read` — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no `crypto_not_entitled` code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today.\n\nA trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.","tags":["scans"],"parameters":["44d3b8a7-1d0f-4d80-ab6f-dd948d5a2a7c","6ad950fb-a47c-4e95-afa4-ae72709b08c6","e02e701f-16ff-42ec-8ef2-49f8619ab395"],"responses":{"200":"12ce241c-b6c5-48b0-8cef-6e016e72f402","400":"99c44213-11d8-41e7-882a-4beed9822992","401":"ae1d1a30-67ae-47f2-a0f8-c8918552e81a","403":"137026b1-dec7-4549-851f-0a188b076ce6","404":"67d8df40-bddd-4a7e-bc44-1016752cbb44","500":"08a4fa44-3e85-4111-a680-f831479e35e1"},"method":"get","type":"path","servers":["78824d01-63cc-41fd-9d19-c3590c2af6c2"],"security":["044b1aa4-bef2-430b-bd04-5a8e9add18c6"],"path":"/v1/crypto/posture","baseUrlOptions":["https://{tenant}.earnie.dev"],"title":"The organization's crypto posture across a scope of projects","codeSamples":[],"requiredOnlyExamples":false,"requestExampleType":"generated","responseExampleType":"generated"},"dependencies":{"parameters":{"44d3b8a7-1d0f-4d80-ab6f-dd948d5a2a7c":{"name":"projects","in":"query","required":false,"description":"Comma-separated project ids to narrow the scope to. Omitted means every non-archived project in the organization. A value that is not a uuid is a 400; an id the caller cannot see is dropped.","schema":{"type":"string","isRequired":false,"description":"Comma-separated project ids to narrow the scope to. Omitted means every non-archived project in the organization. A value that is not a uuid is a 400; an id the caller cannot see is dropped.","uniqueKey":"","typeLabel":"string"}},"6ad950fb-a47c-4e95-afa4-ae72709b08c6":{"name":"batch","in":"query","required":false,"description":"A bulk import batch id. Narrows the scope to the projects that batch has created so far, resolved on the server so the request stays one id long however large the import. Cannot be combined with `projects`. A batch that does not exist in the caller's organization is a 404; a batch that has created no project yet answers an empty scope, never the whole organization.","schema":{"type":"string","format":"uuid","isRequired":false,"description":"A bulk import batch id. Narrows the scope to the projects that batch has created so far, resolved on the server so the request stays one id long however large the import. Cannot be combined with `projects`. A batch that does not exist in the caller's organization is a 404; a batch that has created no project yet answers an empty scope, never the whole organization.","uniqueKey":"","typeLabel":"string\u003cuuid>"}},"e02e701f-16ff-42ec-8ef2-49f8619ab395":{"name":"include_archived","in":"query","required":false,"schema":{"type":"boolean","default":false,"isRequired":false,"uniqueKey":"","typeLabel":"boolean"}}},"responses":{"12ce241c-b6c5-48b0-8cef-6e016e72f402":{"description":"The scope's crypto posture. Always 200 for an authorized caller — an unmeasured estate, an unentitled organization and a failed findings read all return this shape with `crypto` absent, never an error and never zeros.","content":{"application/json":{"schema":{"type":"object","description":"Two halves answering two different questions. The scope counts — `projects_in_scope`, `projects_scanned`, `projects_not_scanned` — say how much of the estate the numbers cover and are ALWAYS present. `crypto` carries the numbers, and is ABSENT when no project in scope has been measured.\n\nCoverage is reported as its own field rather than left to subtraction, because a reader who has to compute it will not. \"1,240 quantum-vulnerable assets\" stated over a fifth of the estate is a different sentence from the same number stated over all of it, and an estate surface that cannot say which one it is saying is worse than no surface. Two invariants hold: `projects_scanned + projects_not_scanned == projects_in_scope`, and when `crypto` is present, `projects_scanned == len(crypto.projects)`.\n\nA project is MEASURED when it has EVER completed a `crypto` scan stage on a completed scan, OR it still holds active crypto findings. Both halves are load-bearing: the stage alone loses a project whose findings outlived the scan that found them, and the findings alone report a project the scanner cleared as never scanned. An unmeasured project is counted in `projects_not_scanned`, is absent from `crypto.projects`, and contributes to NO total on this payload. It is never folded in as a zero — that coercion turns \"unknown\" into \"verified safe\", which on a governance surface is the single error this response exists to prevent.\n\nTHAT RULE IS DELIBERATELY WIDER THAN THE PROJECT CARD'S, and the two are not interchangeable. `ProjectCryptoSummary.crypto` is present when the POSTURE SOURCE SCAN ran crypto to completion, or the project holds active crypto findings. This endpoint asks instead whether ANY completed scan of the project ever completed a crypto stage, which is a strict superset. The divergence has exactly one shape: scan A completes with a completed crypto stage and zero findings; scan B completes later, without crypto, and becomes the posture source. That project's own page reads \"Crypto not scanned\", while here it is counted in `projects_scanned`, listed in `crypto.projects` with zeros, and counted in `export_readiness.ready_projects`.\n\nThe wider rule is the right one at this altitude: a project the scanner ran and cleared IS measured, and the estate is where calling it unmeasured most distorts the coverage answer. The crypto NUMBERS still agree with the project card — such a project contributes zeros to every count — so the divergence is in coverage accounting (`projects_scanned`, `export_readiness.ready_projects`), never in a crypto total. `crypto.projects[].last_crypto_scan_at` is what lets a reader see it: it dates the older crypto scan the project page no longer reports.\n\nAn organization without the crypto scanner receives exactly this response with `crypto` absent and every project counted in `projects_not_scanned` — byte-identical to an entitled organization that has never run a crypto scan, and reached through the same code path rather than through an entitlement branch. There is deliberately no `403` and no crypto-specific error code: a distinguishable refusal would advertise entitlement state on a read surface that carries none today.","required":["projects_in_scope","projects_scanned","projects_not_scanned"],"properties":{"projects_in_scope":{"type":"integer","description":"Projects this request resolved: the caller's organization, narrowed by `projects`, by `include_archived`, and by any project binding on the principal. The denominator every other count here is read against.","isRequired":true,"uniqueKey":"projects_in_scope","typeLabel":"integer"},"projects_scanned":{"type":"integer","description":"In-scope projects that are MEASURED under the union above. Equals `len(crypto.projects)` whenever `crypto` is present, and 0 whenever it is absent.\n\nA measured project with zero crypto findings is counted HERE and contributes real zeros to every total. \"Scanned and clean\" and \"never scanned\" stay distinguishable at estate altitude, which is exactly where conflating them does the most damage: a clean headline covering projects nobody ever looked at is the report a CISO would act on and should not.","isRequired":true,"uniqueKey":"projects_scanned","typeLabel":"integer"},"projects_not_scanned":{"type":"integer","description":"In-scope projects that are NOT measured. Its own field rather than `projects_in_scope − projects_scanned`, because a client that has to derive coverage will render the total without it.\n\nThis is also where a failed read lands. When the crypto findings for this scope cannot be read, the response degrades to ABSENCE — `crypto` omitted, every project counted here — never to zeros and never to an empty estate. That deliberately makes an outage indistinguishable from an unscanned estate ON THE WIRE; the server's WARN log is where an operator learns which one it was. The alternative shapes are both worse: zeros would claim a clean estate the store never confirmed, and a 500 would take down a page whose other cards are fine.","isRequired":true,"uniqueKey":"projects_not_scanned","typeLabel":"integer"},"crypto":{"type":"object","description":"The aggregate itself. OPTIONAL, and its presence is the not-measured discriminator, exactly as `ProjectCryptoSummary.crypto` is for one project: ABSENT means no project in scope has ever completed a crypto stage and none holds an active crypto finding (or the read failed); PRESENT with all-zero counts means the scanner ran across the measured projects and found nothing.\n\nClients must never read absence as \"clean\" nor zeros as \"not scanned\", and must never render a total from this object without also rendering `projects_not_scanned` beside it.","required":["findings_total","assets_total","reachable_weak","quantum_vulnerable","quantum_unknown","severity","pqc_status","export_readiness","triaged","top_algorithms","projects"],"properties":{"findings_total":{"type":"integer","description":"Rule-level crypto finding rows (occurrence × rule) summed across every measured project. Inventory: triage-blind.\n\nA finding whose evidence could not be PARSED is not counted here. Its evidence never resolved into an asset, so counting it would put a row in the inventory that no asset, severity or family breakdown can account for. `export_readiness.total_findings` DOES count it, because readiness has to fail closed on unparseable evidence rather than quietly drop it. The two counts therefore have different populations and `export_readiness.total_findings` can legitimately EXCEED this number — see its own description. A client must not present either as a subset of the other.","isRequired":true,"uniqueKey":"crypto.findings_total","typeLabel":"integer"},"assets_total":{"type":"integer","description":"Distinct crypto assets summed across every measured project — each project's own distinct count, added. See the schema description: this is NOT a global distinct count and must not be presented as one.\n\nInventory: triage-blind. Deciding a finding does not remove the algorithm from the build.","isRequired":true,"uniqueKey":"crypto.assets_total","typeLabel":"integer"},"reachable_weak":{"type":"integer","description":"OUTSTANDING findings that are reachable AND at effective severity high or critical, summed across measured projects — the estate headline, and the same quantity `ProjectPostureRow.weak_crypto` reports per project.\n\nTriage-aware: resolving a reachable-high finding as `false_positive` reduces this by one and raises `triaged.reachable_weak` by one.","isRequired":true,"uniqueKey":"crypto.reachable_weak","typeLabel":"integer"},"quantum_vulnerable":{"type":"integer","description":"Distinct assets Shor's algorithm breaks, summed per project, on any CycloneDX asset type whose algorithm family resolves. Certificates, protocols and key material are counted; hashes, symmetric ciphers, MACs and KDFs are not, because Grover is a key-size recommendation rather than a migration item.\n\nThis is the OMB M-23-02 number — the estate's PQC migration backlog. Triage-aware: a dispositioned asset is not backlog.","isRequired":true,"uniqueKey":"crypto.quantum_vulnerable","typeLabel":"integer"},"quantum_unknown":{"type":"integer","description":"Distinct assets whose post-quantum status could not be judged — the algorithm family is absent, or no curated table covers it. NOT vulnerable and NOT safe.\n\nCarried so a reader can state how much of the estate could not be judged. Without it, `assets_total − quantum_vulnerable` reads as a quantum-safe population nobody ever measured.","isRequired":true,"uniqueKey":"crypto.quantum_unknown","typeLabel":"integer"},"severity":{"type":"object","description":"The effective-severity distribution of OUTSTANDING crypto findings, summed across the measured projects.\n\nFive explicit buckets, all required. They partition the outstanding crypto findings, so none of them may be derived as a remainder of the others against `findings_total` — `findings_total` is inventory and includes the triaged population these buckets exclude.","required":["critical","high","medium","low","info"],"properties":{"critical":{"type":"integer","isRequired":true,"uniqueKey":"crypto.severity.critical","typeLabel":"integer"},"high":{"type":"integer","isRequired":true,"uniqueKey":"crypto.severity.high","typeLabel":"integer"},"medium":{"type":"integer","isRequired":true,"uniqueKey":"crypto.severity.medium","typeLabel":"integer"},"low":{"type":"integer","isRequired":true,"uniqueKey":"crypto.severity.low","typeLabel":"integer"},"info":{"type":"integer","isRequired":true,"uniqueKey":"crypto.severity.info","typeLabel":"integer"}},"isRequired":true,"uniqueKey":"crypto.severity","typeLabel":"object"},"pqc_status":{"type":"object","description":"The complete four-state post-quantum verdict distribution over DISTINCT outstanding crypto assets, summed per project.\n\nAll four states are sent explicitly, and `safe` in particular must never be derived as a remainder. `unassessed` is a real, separate answer — the algorithm family is absent or no curated table covers it — and folding it into `safe` is the overstatement the four-state verdict exists to prevent: it converts \"we could not judge this\" into \"this is fine\".\n\n`vulnerable` mirrors `EstateCryptoAggregate.quantum_vulnerable` and `unassessed` mirrors `quantum_unknown`; the two headline fields are kept for parity with `CryptoRollup`, and this object is what a client should render a distribution from.","required":["vulnerable","safe","unassessed","not_applicable"],"properties":{"vulnerable":{"type":"integer","description":"Distinct assets Shor's algorithm breaks. The migration backlog.","isRequired":true,"uniqueKey":"crypto.pqc_status.vulnerable","typeLabel":"integer"},"safe":{"type":"integer","description":"Distinct assets a curated table judged post-quantum safe. A real measurement, never a subtraction.","isRequired":true,"uniqueKey":"crypto.pqc_status.safe","typeLabel":"integer"},"unassessed":{"type":"integer","description":"Distinct assets whose post-quantum status could not be judged. NOT vulnerable and NOT safe.","isRequired":true,"uniqueKey":"crypto.pqc_status.unassessed","typeLabel":"integer"},"not_applicable":{"type":"integer","description":"Distinct assets for which the question does not arise — a hash or a symmetric cipher has nothing for Shor to attack, so it is not migration work and must not be reported as either verdict.","isRequired":true,"uniqueKey":"crypto.pqc_status.not_applicable","typeLabel":"integer"}},"isRequired":true,"uniqueKey":"crypto.pqc_status","typeLabel":"object"},"export_readiness":{"type":"object","description":"EAR export-control evidence completeness across the estate, in the two units that answer two different questions.\n\nThe PROJECT counts (`ready_projects`, `incomplete_projects`, `stale_vintage_projects`) say how many products are shippable today; they partition `EstateCryptoPosture.projects_scanned` exactly. The FINDING counts are the summed per-project totals and say how much evidence work is left. Neither alone is enough: a project count cannot size the work, and a finding count cannot say how many products are clear.\n\nRead `ready_projects` with the denominator in view. A measured project with no crypto findings at all is READY — there is no evidence to be incomplete about — so a high `ready_projects` over a low `total_findings` describes an estate with little cryptography, not one with thorough export evidence. The finding counts beside it are how a reader tells those apart.\n\nLike the per-project rollup, this is the ONE part of the aggregate that does not follow the outstanding-work rule, and the exception is deliberate: its population is the CBOM's — every active finding except `false_positive` — because the question is about what the estate SHIPS. Scoping it to outstanding work would let a project whose crypto was all confirmed real report ready over zero gathered signals.\n\nEvidence completeness only. Nothing here classifies anything: no ECCN is derived, stated or implied.","required":["ready_projects","incomplete_projects","stale_vintage_projects","resolved_findings","unresolved_findings","total_findings","stale_findings"],"properties":{"ready_projects":{"type":"integer","description":"Measured projects whose every in-scope finding carries complete decisive evidence under the regime version shipping today.","isRequired":true,"uniqueKey":"crypto.export_readiness.ready_projects","typeLabel":"integer"},"incomplete_projects":{"type":"integer","description":"Measured projects with evidence missing or unresolved. The remedy is better detection or curation.","isRequired":true,"uniqueKey":"crypto.export_readiness.incomplete_projects","typeLabel":"integer"},"stale_vintage_projects":{"type":"integer","description":"Measured projects that HAVE export evidence, none of it computed under the current regime version. Nothing is wrong with the code; the measurement is simply older than the regime and a re-scan refreshes it. Split out from `incomplete_projects` because after a regime bump this is momentarily the entire estate, and reporting that as ordinary incompleteness would send every team hunting for a problem that does not exist.","isRequired":true,"uniqueKey":"crypto.export_readiness.stale_vintage_projects","typeLabel":"integer"},"resolved_findings":{"type":"integer","description":"Unique findings with complete decisive current EAR evidence, summed across measured projects.","isRequired":true,"uniqueKey":"crypto.export_readiness.resolved_findings","typeLabel":"integer"},"unresolved_findings":{"type":"integer","description":"Unique findings with incomplete current EAR evidence, summed across measured projects. This is the size of the evidence work.","isRequired":true,"uniqueKey":"crypto.export_readiness.unresolved_findings","typeLabel":"integer"},"total_findings":{"type":"integer","description":"The denominator `resolved_findings` and `unresolved_findings` partition; always equals their sum. Distinct from `EstateCryptoAggregate.findings_total`, which counts rule-level rows — a progress bar computed against the wrong one silently overstates completeness wherever a finding carries several rules.\n\nThe two populations differ a SECOND way, and it runs the other direction. A finding whose evidence could not be parsed is counted HERE, as unresolved: readiness must fail closed on evidence it cannot read. `EstateCryptoAggregate.findings_total` omits that same finding, because its evidence never resolved into an asset. A project whose only crypto finding has unparseable evidence therefore reports `findings_total: 0` beside `export_readiness.total_findings: 1`. Both numbers are right for their own question; neither is a subset of the other, and a client must never render them together as \"1 of 0\".","isRequired":true,"uniqueKey":"crypto.export_readiness.total_findings","typeLabel":"integer"},"stale_findings":{"type":"integer","description":"Findings whose only export evidence predates the current regime version, summed across measured projects. Reported even when no project is in the `stale_vintage` state, so a partially re-scanned estate can say how much evidence still predates the bump.","isRequired":true,"uniqueKey":"crypto.export_readiness.stale_findings","typeLabel":"integer"}},"isRequired":true,"uniqueKey":"crypto.export_readiness","typeLabel":"object"},"triaged":{"type":"object","description":"The active crypto findings the outstanding-work counts on `EstateCryptoAggregate` EXCLUDE, summed across measured projects, so a decision MOVES a number instead of deleting one at estate altitude too. Without it a falling estate headline is indistinguishable from cryptography leaving the build.\n\nThe predicate is inherited from the project rollup and is NOT redefined here: a finding is excluded when it is suppressed OR superseded by a rule — the same predicate the policy gate applies. `confirm_usage` is not among them: it resolves WITHOUT suppression so it keeps gate impact, and it is reported alongside `total` rather than inside it.\n\nThe shape mirrors `CryptoTriagedRollup` deliberately — a reader who learns the vocabulary once reads both — but it is a separate schema because one field's meaning changes with altitude: `quantum_vulnerable_assets` is a sum of per-project distinct counts here, exactly as `assets_total` is, while on `CryptoTriagedRollup` it is one project's distinct count. Sharing the schema would have carried a project-scoped distinctness claim onto an estate payload where it is not true.\n\n`accepted_risk` and `false_positive` are disjoint subsets of `total` and need NOT sum to it: a rule supersession or a standalone suppression excludes a finding while carrying no crypto reason. Clients render the unattributed remainder rather than publishing arithmetic that does not add up.","required":["total","confirmed_usage","accepted_risk","false_positive","reachable_weak","quantum_vulnerable_assets"],"properties":{"total":{"type":"integer","description":"Every finding the outstanding-work counts exclude, whatever put it there.","isRequired":true,"uniqueKey":"crypto.triaged.total","typeLabel":"integer"},"confirmed_usage":{"type":"integer","description":"Resolved with `confirm_usage` — real cryptography, acknowledged. NOT part of `total` and NOT excluded from any outstanding count, because that verb is non-suppressing by design. Carried so a client can say how much of the queue has been looked at.","isRequired":true,"uniqueKey":"crypto.triaged.confirmed_usage","typeLabel":"integer"},"accepted_risk":{"type":"integer","description":"Resolved with `accepted_risk` — real cryptography the project accepts. Suppressing, so it is part of `total`.","isRequired":true,"uniqueKey":"crypto.triaged.accepted_risk","typeLabel":"integer"},"false_positive":{"type":"integer","description":"Resolved with `false_positive` — not an actual cryptographic usage. Suppressing, so it is part of `total`.","isRequired":true,"uniqueKey":"crypto.triaged.false_positive","typeLabel":"integer"},"reachable_weak":{"type":"integer","description":"The subset of `total` that would have counted toward `EstateCryptoAggregate.reachable_weak`. Carried so the excluded slice can be rendered directly instead of derived across the inventory/outstanding line.","isRequired":true,"uniqueKey":"crypto.triaged.reachable_weak","typeLabel":"integer"},"quantum_vulnerable_assets":{"type":"integer","description":"Assets that would have counted toward `EstateCryptoAggregate.quantum_vulnerable` but whose every sighting is excluded — summed per project, like every other asset count here.\n\nAn asset with even one live sighting stays in `quantum_vulnerable` and is NOT counted here: deciding one of four call sites has not migrated the key. The two therefore never describe the same asset.","isRequired":true,"uniqueKey":"crypto.triaged.quantum_vulnerable_assets","typeLabel":"integer"}},"isRequired":true,"uniqueKey":"crypto.triaged","typeLabel":"object"},"top_algorithms":{"type":"array","items":{"type":"object","description":"One algorithm family's aggregate in the crypto rollup.","required":["family","count","severity","quantum_safe","reachable"],"properties":{"family":{"type":"string","description":"Canonical algorithm family (e.g. MD5, SHA-2, RSA). Producer spellings fold onto the curated key, so \"aes\" and \"AES\" are one row; an uncurated family keeps its own spelling.","isRequired":true,"uniqueKey":"crypto.top_algorithms.items.[INDEX].family","typeLabel":"string"},"count":{"type":"integer","description":"Crypto findings sighting this family.","isRequired":true,"uniqueKey":"crypto.top_algorithms.items.[INDEX].count","typeLabel":"integer"},"severity":{"type":"string","enum":["info","low","medium","high","critical"],"description":"Highest effective severity among the family's findings.","isRequired":true,"uniqueKey":"crypto.top_algorithms.items.[INDEX].severity","typeLabel":"enum\u003cstring>"},"quantum_safe":{"type":"boolean","description":"DEPRECATED — the boolean projection of pqc_status. False when ANY of the family's sighted assets is quantum-vulnerable or unassessed; fail-closed, so an uncurated family is never asserted safe.","isRequired":true,"uniqueKey":"crypto.top_algorithms.items.[INDEX].quantum_safe","typeLabel":"boolean"},"reachable":{"type":"boolean","description":"True when at least one of the family's findings is reachable.","isRequired":true,"uniqueKey":"crypto.top_algorithms.items.[INDEX].reachable","typeLabel":"boolean"}},"uniqueKey":"crypto.top_algorithms.items.[INDEX]","typeLabel":"object"},"description":"The most-sighted algorithm families across the estate, ordered by summed finding count DESC then family ASC, capped at 5 entries. Always present — an empty array when no algorithm assets were sighted. Triage-aware, like the counts it breaks down.\n\nONE CAVEAT, and it is the only field on this object that is not derivable from `projects` by addition. Each project's own `top_algorithms` is already capped at 5 server-side, and this list is merged from those capped lists. A family that ranks sixth or lower in EVERY project can therefore be missing here even though its estate-wide total is large. Families beyond either cap still count toward every total above; only this breakdown is truncated. A client must treat it as \"the largest families we can name\", never as an exhaustive estate ranking, and must never derive a total from it.","isRequired":true,"uniqueKey":"crypto.top_algorithms","typeLabel":"object[]"},"projects":{"type":"array","items":{"type":"object","description":"One measured project's contribution to the estate totals — the same numbers that project's own Cryptography card renders, carried here so the estate totals are verifiable by addition and so the card can rank projects and link into each one.\n\nOnly MEASURED projects appear. Every field below is this project's own value under exactly the rules the aggregate documents, including per-project asset distinctness: `assets_total` here is distinct within this project, and the estate `assets_total` is the sum of these.","required":["project_id","slug","name","findings_total","assets_total","reachable_weak","quantum_vulnerable","quantum_unknown","severity","pqc_status","triaged","export_readiness"],"properties":{"project_id":{"type":"string","format":"uuid","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].project_id","typeLabel":"string\u003cuuid>"},"slug":{"type":"string","description":"Carried so the client can build the drill-down link `/projects/{slug}/review?lens=crypto` without a second lookup. That query is one the workspace actually parses; a client must not append severity or `pqc_status` filters the page would silently ignore, because a link that looks filtered and is not is worse than a link that does not claim to be.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].slug","typeLabel":"string"},"name":{"type":"string","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].name","typeLabel":"string"},"findings_total":{"type":"integer","description":"This project's rule-level crypto finding rows. Inventory.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].findings_total","typeLabel":"integer"},"assets_total":{"type":"integer","description":"This project's distinct crypto assets. Inventory.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].assets_total","typeLabel":"integer"},"reachable_weak":{"type":"integer","description":"This project's outstanding reachable high/critical findings — the same quantity `ProjectPostureRow.weak_crypto` reports for it.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].reachable_weak","typeLabel":"integer"},"quantum_vulnerable":{"type":"integer","description":"This project's distinct quantum-vulnerable assets. Outstanding work.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].quantum_vulnerable","typeLabel":"integer"},"quantum_unknown":{"type":"integer","description":"This project's distinct unjudgeable assets. Outstanding work.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].quantum_unknown","typeLabel":"integer"},"severity":{"type":"object","description":"The effective-severity distribution of OUTSTANDING crypto findings, summed across the measured projects.\n\nFive explicit buckets, all required. They partition the outstanding crypto findings, so none of them may be derived as a remainder of the others against `findings_total` — `findings_total` is inventory and includes the triaged population these buckets exclude.","required":["critical","high","medium","low","info"],"properties":{"critical":{"type":"integer","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].severity.critical","typeLabel":"integer"},"high":{"type":"integer","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].severity.high","typeLabel":"integer"},"medium":{"type":"integer","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].severity.medium","typeLabel":"integer"},"low":{"type":"integer","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].severity.low","typeLabel":"integer"},"info":{"type":"integer","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].severity.info","typeLabel":"integer"}},"isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].severity","typeLabel":"object"},"pqc_status":{"type":"object","description":"The complete four-state post-quantum verdict distribution over DISTINCT outstanding crypto assets, summed per project.\n\nAll four states are sent explicitly, and `safe` in particular must never be derived as a remainder. `unassessed` is a real, separate answer — the algorithm family is absent or no curated table covers it — and folding it into `safe` is the overstatement the four-state verdict exists to prevent: it converts \"we could not judge this\" into \"this is fine\".\n\n`vulnerable` mirrors `EstateCryptoAggregate.quantum_vulnerable` and `unassessed` mirrors `quantum_unknown`; the two headline fields are kept for parity with `CryptoRollup`, and this object is what a client should render a distribution from.","required":["vulnerable","safe","unassessed","not_applicable"],"properties":{"vulnerable":{"type":"integer","description":"Distinct assets Shor's algorithm breaks. The migration backlog.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].pqc_status.vulnerable","typeLabel":"integer"},"safe":{"type":"integer","description":"Distinct assets a curated table judged post-quantum safe. A real measurement, never a subtraction.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].pqc_status.safe","typeLabel":"integer"},"unassessed":{"type":"integer","description":"Distinct assets whose post-quantum status could not be judged. NOT vulnerable and NOT safe.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].pqc_status.unassessed","typeLabel":"integer"},"not_applicable":{"type":"integer","description":"Distinct assets for which the question does not arise — a hash or a symmetric cipher has nothing for Shor to attack, so it is not migration work and must not be reported as either verdict.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].pqc_status.not_applicable","typeLabel":"integer"}},"isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].pqc_status","typeLabel":"object"},"triaged":{"type":"object","description":"The active crypto findings the outstanding-work counts on `EstateCryptoAggregate` EXCLUDE, summed across measured projects, so a decision MOVES a number instead of deleting one at estate altitude too. Without it a falling estate headline is indistinguishable from cryptography leaving the build.\n\nThe predicate is inherited from the project rollup and is NOT redefined here: a finding is excluded when it is suppressed OR superseded by a rule — the same predicate the policy gate applies. `confirm_usage` is not among them: it resolves WITHOUT suppression so it keeps gate impact, and it is reported alongside `total` rather than inside it.\n\nThe shape mirrors `CryptoTriagedRollup` deliberately — a reader who learns the vocabulary once reads both — but it is a separate schema because one field's meaning changes with altitude: `quantum_vulnerable_assets` is a sum of per-project distinct counts here, exactly as `assets_total` is, while on `CryptoTriagedRollup` it is one project's distinct count. Sharing the schema would have carried a project-scoped distinctness claim onto an estate payload where it is not true.\n\n`accepted_risk` and `false_positive` are disjoint subsets of `total` and need NOT sum to it: a rule supersession or a standalone suppression excludes a finding while carrying no crypto reason. Clients render the unattributed remainder rather than publishing arithmetic that does not add up.","required":["total","confirmed_usage","accepted_risk","false_positive","reachable_weak","quantum_vulnerable_assets"],"properties":{"total":{"type":"integer","description":"Every finding the outstanding-work counts exclude, whatever put it there.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].triaged.total","typeLabel":"integer"},"confirmed_usage":{"type":"integer","description":"Resolved with `confirm_usage` — real cryptography, acknowledged. NOT part of `total` and NOT excluded from any outstanding count, because that verb is non-suppressing by design. Carried so a client can say how much of the queue has been looked at.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].triaged.confirmed_usage","typeLabel":"integer"},"accepted_risk":{"type":"integer","description":"Resolved with `accepted_risk` — real cryptography the project accepts. Suppressing, so it is part of `total`.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].triaged.accepted_risk","typeLabel":"integer"},"false_positive":{"type":"integer","description":"Resolved with `false_positive` — not an actual cryptographic usage. Suppressing, so it is part of `total`.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].triaged.false_positive","typeLabel":"integer"},"reachable_weak":{"type":"integer","description":"The subset of `total` that would have counted toward `EstateCryptoAggregate.reachable_weak`. Carried so the excluded slice can be rendered directly instead of derived across the inventory/outstanding line.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].triaged.reachable_weak","typeLabel":"integer"},"quantum_vulnerable_assets":{"type":"integer","description":"Assets that would have counted toward `EstateCryptoAggregate.quantum_vulnerable` but whose every sighting is excluded — summed per project, like every other asset count here.\n\nAn asset with even one live sighting stays in `quantum_vulnerable` and is NOT counted here: deciding one of four call sites has not migrated the key. The two therefore never describe the same asset.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].triaged.quantum_vulnerable_assets","typeLabel":"integer"}},"isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].triaged","typeLabel":"object"},"export_readiness":{"type":"object","description":"This project's own readiness rollup, in exactly the shape and with exactly the semantics the project surface uses. Reused rather than re-modelled because it IS the same measurement; the estate-level `EstateCryptoExportReadiness` is a different shape only because a project count and a finding count answer different questions.","required":["ready","state","unresolved_findings","resolved_findings","total_findings","stale_findings"],"properties":{"ready":{"type":"boolean","description":"True when every active finding has complete decisive current EAR evidence; support-purpose tests are non-decisive. Exactly equivalent to `state == ready`.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].export_readiness.ready","typeLabel":"boolean"},"state":{"type":"string","enum":["ready","incomplete","stale_vintage"],"description":"Export-evidence readiness verdict. `ready`: every active finding has complete decisive evidence under the regime version shipping today. `incomplete`: some current-vintage evidence is missing or unresolved. `stale_vintage`: the project has export evidence, but none of it was computed under the current regime version — nothing is wrong with the code, the measurement is simply older than the regime, and re-scanning refreshes it. Reporting that case as `ready` would let a regime bump read as good news across every project that has not re-scanned.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].export_readiness.state","typeLabel":"enum\u003cstring>"},"stale_findings":{"type":"integer","description":"Active findings whose only export evidence was computed under a superseded regime version. Reported even when `state` is not `stale_vintage`, so a partially re-scanned project can say how much of its evidence still predates the bump.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].export_readiness.stale_findings","typeLabel":"integer"},"unresolved_findings":{"type":"integer","description":"Number of unique active findings with incomplete current EAR evidence.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].export_readiness.unresolved_findings","typeLabel":"integer"},"resolved_findings":{"type":"integer","description":"Unique active findings whose decisive current EAR evidence IS complete. Carried explicitly rather than left to the client as `total − unresolved`: `unresolved_findings` counts unique findings while `CryptoRollup.findings_total` counts rule-level rows, so that subtraction is wrong wherever one finding carries several rules.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].export_readiness.resolved_findings","typeLabel":"integer"},"total_findings":{"type":"integer","description":"The denominator `resolved_findings` and `unresolved_findings` partition — unique active findings considered for EAR evidence. Always equals their sum. Distinct from `CryptoRollup.findings_total`, which counts rule-level rows.","isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].export_readiness.total_findings","typeLabel":"integer"}},"isRequired":true,"uniqueKey":"crypto.projects.items.[INDEX].export_readiness","typeLabel":"object"},"last_crypto_scan_at":{"oneOf":[{"type":"string","format":"date-time","description":"finished_at of this project's most recent COMPLETED scan that ran the crypto stage to completion — the same fact `ProjectCryptoSummary.last_crypto_scan_at` reports for one project, at estate altitude.\n\nNULL when no scan of this project ever ran crypto to completion. For a project listed here that means it appears ONLY because active crypto findings outlived the scan that produced them, and a client should say so rather than imply the numbers are as fresh as the rest of the page.\n\nProject-scoped, NOT anchored to any posture source scan: the answer is about the project's crypto history, not about whichever scan defines its posture today. A project whose newest scan skipped crypto still reports the older crypto scan's timestamp.\n\nThis is the field that says WHICH projects' crypto numbers are stale — the coverage question this estate exists to answer. `projects_not_scanned` counts the projects nobody measured; this dates the measurement for the ones somebody did, so a total is readable with its vintage per project instead of as one undifferentiated \"now\". A zero time is never sent and must never be rendered as a date: a project measured with no recorded finished_at reports null here, which is \"measured, freshness unknown\", not \"never measured\".","uniqueKey":"crypto.projects.items.[INDEX].last_crypto_scan_at.oneOf.0","typeLabel":"string\u003cdate-time>"},{"type":"null","format":"date-time","description":"finished_at of this project's most recent COMPLETED scan that ran the crypto stage to completion — the same fact `ProjectCryptoSummary.last_crypto_scan_at` reports for one project, at estate altitude.\n\nNULL when no scan of this project ever ran crypto to completion. For a project listed here that means it appears ONLY because active crypto findings outlived the scan that produced them, and a client should say so rather than imply the numbers are as fresh as the rest of the page.\n\nProject-scoped, NOT anchored to any posture source scan: the answer is about the project's crypto history, not about whichever scan defines its posture today. A project whose newest scan skipped crypto still reports the older crypto scan's timestamp.\n\nThis is the field that says WHICH projects' crypto numbers are stale — the coverage question this estate exists to answer. `projects_not_scanned` counts the projects nobody measured; this dates the measurement for the ones somebody did, so a total is readable with its vintage per project instead of as one undifferentiated \"now\". A zero time is never sent and must never be rendered as a date: a project measured with no recorded finished_at reports null here, which is \"measured, freshness unknown\", not \"never measured\".","uniqueKey":"crypto.projects.items.[INDEX].last_crypto_scan_at.oneOf.1","typeLabel":"null"}],"uniqueKey":"crypto.projects.items.[INDEX].last_crypto_scan_at","typeLabel":"string\u003cdate-time> | null"}},"uniqueKey":"crypto.projects.items.[INDEX]","typeLabel":"object"},"description":"One entry per MEASURED project, so every total above can be checked by addition rather than trusted. Always present — an empty array cannot occur while `crypto` itself is present, because an aggregate with no measured project is reported as absence instead.\n\nUnmeasured projects are NOT listed. Absence from this array is the per-project not-measured signal, and it is the same fact `projects_not_scanned` counts. A client rendering a per-project crypto column must read a project missing here as \"Not scanned\" and must NOT render a `0` for it. Where this array and `ProjectPostureRow.weak_crypto` disagree about whether a project was measured, THIS wins: it knows about completed crypto stages and the posture row does not.","isRequired":true,"uniqueKey":"crypto.projects","typeLabel":"object[]"},"datasets":{"type":"object","description":"The two curated datasets that decided what the findings behind this rollup mean: the algorithm/protocol/key-material risk table that set every severity and the regime-versioned export-control dataset that answered every export test.\n\nIt is a property of the BINARY that served this summary, not of the scan — the tables ship inside the process, so the rollup states the curation a reader is looking at right now. Per-finding provenance is a different question and lives on the finding's own evidence (`risk_table_version`, `export_regime_version`), where the vintage is scan-anchored.\n\nEach dataset's identity and its review date travel TOGETHER, and a half-populated pair is omitted entirely rather than sent with a blank. The two are separate claims — one says which curation this is, the other says a human looked at it — and an identity with no review date reads as a fresher claim than the evidence supports. A client that receives no pair MUST say nothing about currency; \"last reviewed\" followed by a blank is the one sentence an unstamped payload cannot make.\n\nThe whole object is optional so a client reading an older server's payload renders nothing rather than an empty date.","properties":{"risk_table_version":{"type":"string","description":"The crypto risk table's curation vintage, e.g. `nist-2026-08`. Present only together with `risk_table_reviewed_at`.","uniqueKey":"crypto.datasets.risk_table_version","typeLabel":"string"},"risk_table_reviewed_at":{"type":"string","description":"The date (`YYYY-MM-DD`) a human last read every risk row against the standards document it cites. Present only together with `risk_table_version`.\n\nAn opaque string, deliberately not `format: date`: a typed date has a zero value, and a zero value renders as `0001-01-01` — a real-looking review date nobody ever claimed. Absent is the only honest way to say \"unstamped\", and a string that is either the curated value or missing cannot degrade into a fabricated one.","uniqueKey":"crypto.datasets.risk_table_reviewed_at","typeLabel":"string"},"export_dataset_id":{"type":"string","description":"The export-control dataset's composed regime identity, e.g. `ear-2026-08` — regime plus vintage, because the vintage alone does not say which regime stated the test. Present only together with `export_dataset_reviewed_at`.","uniqueKey":"crypto.datasets.export_dataset_id","typeLabel":"string"},"export_dataset_reviewed_at":{"type":"string","description":"The date (`YYYY-MM-DD`) a human last read every export row against its eCFR citation. Present only together with `export_dataset_id`.","uniqueKey":"crypto.datasets.export_dataset_reviewed_at","typeLabel":"string"}},"uniqueKey":"crypto.datasets","typeLabel":"object"}},"uniqueKey":"crypto","typeLabel":"object"}},"uniqueKey":"","typeLabel":"object"},"examples":{"Example":{"title":"Example","value":{"projects_in_scope":123,"projects_scanned":123,"projects_not_scanned":123,"crypto":{"findings_total":123,"assets_total":123,"reachable_weak":123,"quantum_vulnerable":123,"quantum_unknown":123,"severity":{"critical":123,"high":123,"medium":123,"low":123,"info":123},"pqc_status":{"vulnerable":123,"safe":123,"unassessed":123,"not_applicable":123},"export_readiness":{"ready_projects":123,"incomplete_projects":123,"stale_vintage_projects":123,"resolved_findings":123,"unresolved_findings":123,"total_findings":123,"stale_findings":123},"triaged":{"total":123,"confirmed_usage":123,"accepted_risk":123,"false_positive":123,"reachable_weak":123,"quantum_vulnerable_assets":123},"top_algorithms":[{"family":"\u003cstring>","count":123,"severity":"info","quantum_safe":true,"reachable":true}],"projects":[{"project_id":"3c90c3cc-0d44-4b50-8888-8dd25736052a","slug":"\u003cstring>","name":"\u003cstring>","findings_total":123,"assets_total":123,"reachable_weak":123,"quantum_vulnerable":123,"quantum_unknown":123,"severity":{"critical":123,"high":123,"medium":123,"low":123,"info":123},"pqc_status":{"vulnerable":123,"safe":123,"unassessed":123,"not_applicable":123},"triaged":{"total":123,"confirmed_usage":123,"accepted_risk":123,"false_positive":123,"reachable_weak":123,"quantum_vulnerable_assets":123},"export_readiness":{"ready":true,"state":"ready","stale_findings":123,"unresolved_findings":123,"resolved_findings":123,"total_findings":123},"last_crypto_scan_at":"2023-11-07T05:31:56Z"}],"datasets":{"risk_table_version":"\u003cstring>","risk_table_reviewed_at":"\u003cstring>","export_dataset_id":"\u003cstring>","export_dataset_reviewed_at":"\u003cstring>"}}}}},"exampleType":"generated"}},"exampleType":"generated"},"99c44213-11d8-41e7-882a-4beed9822992":{"description":"A value in `projects` or `batch` is not a uuid, or `batch` is combined with `projects` (`invalid_scope`).","content":{"application/json":{"schema":{"type":"object","required":["code","message"],"properties":{"code":{"type":"string","description":"Machine-readable error code. `source_not_available` when WFP upload lands).","isRequired":true,"uniqueKey":"code","typeLabel":"string"},"message":{"type":"string","isRequired":true,"uniqueKey":"message","typeLabel":"string"}},"uniqueKey":"","typeLabel":"object"},"examples":{"Example":{"title":"Example","value":{"code":"\u003cstring>","message":"\u003cstring>"}}},"exampleType":"generated"}},"exampleType":"generated"},"ae1d1a30-67ae-47f2-a0f8-c8918552e81a":{"description":"Not authenticated.","content":{"application/json":{"schema":{"type":"object","required":["code","message"],"properties":{"code":{"type":"string","description":"Machine-readable error code. `source_not_available` when WFP upload lands).","isRequired":true,"uniqueKey":"code","typeLabel":"string"},"message":{"type":"string","isRequired":true,"uniqueKey":"message","typeLabel":"string"}},"uniqueKey":"","typeLabel":"object"},"examples":{"Example":{"title":"Example","value":{"code":"\u003cstring>","message":"\u003cstring>"}}},"exampleType":"generated"}},"exampleType":"generated"},"137026b1-dec7-4549-851f-0a188b076ce6":{"description":"Missing `scans:read`.","content":{"application/json":{"schema":{"type":"object","required":["code","message"],"properties":{"code":{"type":"string","description":"Machine-readable error code. `source_not_available` when WFP upload lands).","isRequired":true,"uniqueKey":"code","typeLabel":"string"},"message":{"type":"string","isRequired":true,"uniqueKey":"message","typeLabel":"string"}},"uniqueKey":"","typeLabel":"object"},"examples":{"Example":{"title":"Example","value":{"code":"\u003cstring>","message":"\u003cstring>"}}},"exampleType":"generated"}},"exampleType":"generated"},"67d8df40-bddd-4a7e-bc44-1016752cbb44":{"description":"`batch` names no import batch in the caller's organization (`import_batch_not_found`).","content":{"application/json":{"schema":{"type":"object","required":["code","message"],"properties":{"code":{"type":"string","description":"Machine-readable error code. `source_not_available` when WFP upload lands).","isRequired":true,"uniqueKey":"code","typeLabel":"string"},"message":{"type":"string","isRequired":true,"uniqueKey":"message","typeLabel":"string"}},"uniqueKey":"","typeLabel":"object"},"examples":{"Example":{"title":"Example","value":{"code":"\u003cstring>","message":"\u003cstring>"}}},"exampleType":"generated"}},"exampleType":"generated"},"08a4fa44-3e85-4111-a680-f831479e35e1":{"description":"The project scope itself could not be resolved. A crypto read failure is NOT an error here — it degrades to an absent aggregate (see `EstateCryptoPosture.projects_not_scanned`).","content":{"application/json":{"schema":{"type":"object","required":["code","message"],"properties":{"code":{"type":"string","description":"Machine-readable error code. `source_not_available` when WFP upload lands).","isRequired":true,"uniqueKey":"code","typeLabel":"string"},"message":{"type":"string","isRequired":true,"uniqueKey":"message","typeLabel":"string"}},"uniqueKey":"","typeLabel":"object"},"examples":{"Example":{"title":"Example","value":{"code":"\u003cstring>","message":"\u003cstring>"}}},"exampleType":"generated"}},"exampleType":"generated"}},"security":{"044b1aa4-bef2-430b-bd04-5a8e9add18c6":{"bearerAuth":{"type":"http","scheme":"bearer","description":"An Earnie API key, sent as `Authorization: Bearer sk_earnie_...`. Create one under Settings > API keys. The key's scopes decide which operations it may call.","scopes":[],"schemeName":"bearerAuth"}}},"servers":{"78824d01-63cc-41fd-9d19-c3590c2af6c2":{"url":"https://{tenant}.earnie.dev","description":"Your Earnie deployment","variables":{"tenant":{"default":"your-company","description":"Your organization's Earnie address, as shown in your browser when you sign in."}}}},"processedSecurityOptions":[{"schemes":[{"scheme":{"type":"http","scheme":"bearer","description":"An Earnie API key, sent as `Authorization: Bearer sk_earnie_...`. Create one under Settings > API keys. The key's scopes decide which operations it may call.","scopes":[],"schemeName":"bearerAuth"},"schema":{"title":"Bearer Auth","type":"string","isRequired":true,"description":"An Earnie API key, sent as `Authorization: Bearer sk_earnie_...`. Create one under Settings > API keys. The key's scopes decide which operations it may call.","format":"bearer","typeLabel":"string\u003cbearer>","deprecated":false},"schemeName":"bearerAuth","name":"Authorization"}],"title":"bearerAuth"}]},"originalFileLocation":"api-reference/earnie/scans-openapi.json"},"subdomain":"scanoss","siteName":"SCANOSS documentation","title":"The organization's crypto posture across a scope of projects - SCANOSS documentation","navMaps":{"firstHrefInVersion":{"v2":{"href":"/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects","matchLevel":0},"v1":{"href":"/en/latest/introduction/what-is-scanoss","matchLevel":4}},"firstHrefInLanguage":{}},"lastModified":"2026-10-07T10:42:12.813Z","originalFileLocation":"earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects.mdx"},"headHtml":"\u003cscript data-mint-head>(function(){var d=document.documentElement,p=null;if(!p){try{p=localStorage.getItem(\"isDarkMode\")}catch(e){}if(p==='true')p='dark';else if(p==='false')p='light';if(p!=='light'\u0026\u0026p!=='dark'\u0026\u0026p!=='system')p=\"system\"}var r=p==='system'?(matchMedia(\"(prefers-color-scheme: dark)\").matches?'dark':'light'):p;d.classList.remove(r==='dark'?'light':'dark');d.classList.add(r);d.setAttribute(\"data-theme-preference\",p)})();\u003c/script>\u003cmeta data-mint-head name=\"description\" content=\"OMB M-23-02\u0026#x27;s federal PQC inventory is posed at exactly this altitude. Org-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as GET /v1/scans/projects:posture narrows one. Scope uses the SAME vocabulary projects:posture accepts — projects and include_archived — so the estate canvas narrows both reads with one control. Ids outside the caller\u0026#x27;s organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403. A SEPARATE endpoint from projects:posture, deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization\u0026#x27;s crypto data rather than its project count. Numbers here are the SUM of the per-project crypto rollups GET /v1/scans/projects/{projectId}/summary returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and crypto.projects carries the per-project values so a client can verify it by addition. See EstateCryptoAggregate for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition. Requires scans:read — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no crypto_not_entitled code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today. A trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.\">\u003cmeta data-mint-head name=\"application-name\" content=\"SCANOSS documentation\">\u003cmeta data-mint-head name=\"generator\" content=\"Mintlify\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"192x192\" href=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon/android-chrome-192x192.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"apple-touch-icon\" type=\"image/png\" sizes=\"180x180\" href=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon/apple-touch-icon.png\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"16x16\" href=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon/favicon-16x16.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"32x32\" href=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon/favicon-32x32.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"shortcut icon\" type=\"image/x-icon\" href=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon/favicon.ico\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"192x192\" href=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon-dark/android-chrome-192x192.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"16x16\" href=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon-dark/favicon-16x16.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"32x32\" href=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon-dark/favicon-32x32.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"shortcut icon\" type=\"image/x-icon\" href=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon-dark/favicon.ico\" media=\"(prefers-color-scheme: dark)\">\u003cmeta data-mint-head property=\"og:title\" content=\"The organization\u0026#x27;s crypto posture across a scope of projects - SCANOSS documentation\">\u003cmeta data-mint-head property=\"og:description\" content=\"OMB M-23-02\u0026#x27;s federal PQC inventory is posed at exactly this altitude. Org-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as GET /v1/scans/projects:posture narrows one. Scope uses the SAME vocabulary projects:posture accepts — projects and include_archived — so the estate canvas narrows both reads with one control. Ids outside the caller\u0026#x27;s organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403. A SEPARATE endpoint from projects:posture, deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization\u0026#x27;s crypto data rather than its project count. Numbers here are the SUM of the per-project crypto rollups GET /v1/scans/projects/{projectId}/summary returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and crypto.projects carries the per-project values so a client can verify it by addition. See EstateCryptoAggregate for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition. Requires scans:read — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no crypto_not_entitled code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today. A trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.\">\u003cmeta data-mint-head property=\"og:site_name\" content=\"SCANOSS documentation\">\u003cmeta data-mint-head property=\"og:url\" content=\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects\">\u003cmeta data-mint-head property=\"og:type\" content=\"website\">\u003cmeta data-mint-head property=\"og:image\" content=\"https://scanoss.mintlify.site/_mintlify/api/og/v2?division=scans\u0026amp;title=The+organization%27s+crypto+posture+across+a+scope+of+projects\u0026amp;description=OMB+M-23-02%27s+federal+PQC+inventory+is+posed+at+exactly+this+altitude.%0A%0AOrg-scoped+by+AUTHENTICATION%2C+not+by+path.+The+organization+is+not+a+path+parameter+here\u0026amp;theme=27507c7cd4c9b47ed5abe8b8\u0026amp;signature=ada90111e5ab51257c7a7ea6744dcfba535704e2e58a79b46d552439db6952f3\">\u003cmeta data-mint-head property=\"og:image:width\" content=\"1200\">\u003cmeta data-mint-head property=\"og:image:height\" content=\"630\">\u003cmeta data-mint-head name=\"twitter:card\" content=\"summary_large_image\">\u003cmeta data-mint-head name=\"twitter:title\" content=\"The organization\u0026#x27;s crypto posture across a scope of projects - SCANOSS documentation\">\u003cmeta data-mint-head name=\"twitter:description\" content=\"OMB M-23-02\u0026#x27;s federal PQC inventory is posed at exactly this altitude. Org-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as GET /v1/scans/projects:posture narrows one. Scope uses the SAME vocabulary projects:posture accepts — projects and include_archived — so the estate canvas narrows both reads with one control. Ids outside the caller\u0026#x27;s organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403. A SEPARATE endpoint from projects:posture, deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization\u0026#x27;s crypto data rather than its project count. Numbers here are the SUM of the per-project crypto rollups GET /v1/scans/projects/{projectId}/summary returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and crypto.projects carries the per-project values so a client can verify it by addition. See EstateCryptoAggregate for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition. Requires scans:read — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no crypto_not_entitled code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today. A trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.\">\u003cmeta data-mint-head name=\"twitter:image\" content=\"https://scanoss.mintlify.site/_mintlify/api/og/v2?division=scans\u0026amp;title=The+organization%27s+crypto+posture+across+a+scope+of+projects\u0026amp;description=OMB+M-23-02%27s+federal+PQC+inventory+is+posed+at+exactly+this+altitude.%0A%0AOrg-scoped+by+AUTHENTICATION%2C+not+by+path.+The+organization+is+not+a+path+parameter+here\u0026amp;theme=27507c7cd4c9b47ed5abe8b8\u0026amp;signature=ada90111e5ab51257c7a7ea6744dcfba535704e2e58a79b46d552439db6952f3\">\u003cmeta data-mint-head name=\"twitter:image:width\" content=\"1200\">\u003cmeta data-mint-head name=\"twitter:image:height\" content=\"630\">\u003cmeta data-mint-head name=\"msapplication-config\" content=\"/mintlify-assets/_mintlify/favicons/scanoss/KZfWE-Zg_gP00ddS/_generated/favicon/browserconfig.xml\">\u003cmeta data-mint-head name=\"apple-mobile-web-app-title\" content=\"SCANOSS documentation\">\u003cmeta data-mint-head name=\"msapplication-TileColor\" content=\"#FF6A1A\">\u003clink data-mint-head rel=\"canonical\" href=\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects\">\u003clink data-mint-head rel=\"alternate\" type=\"application/xml\" href=\"/sitemap.xml\">\u003clink data-mint-head rel=\"alternate\" type=\"text/markdown\" href=\"/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects.md\">\u003cscript data-mint-head type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https://docs.scanoss.com/#organization\",\"name\":\"SCANOSS documentation\",\"url\":\"https://docs.scanoss.com\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https://mintcdn.com/scanoss/9UP7eHL2Z_rQPx8l/scanoss-logo-horizontal-positive.svg?fit=max\u0026auto=format\u0026n=9UP7eHL2Z_rQPx8l\u0026q=85\u0026s=686c4487013423ef804e2e83983c76ef\"}},{\"@type\":\"WebSite\",\"@id\":\"https://docs.scanoss.com#website\",\"name\":\"SCANOSS documentation\",\"url\":\"https://docs.scanoss.com\",\"publisher\":{\"@id\":\"https://docs.scanoss.com/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects#webpage\",\"url\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects\",\"name\":\"The organization's crypto posture across a scope of projects\",\"description\":\"OMB M-23-02's federal PQC inventory is posed at exactly this altitude. Org-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as GET /v1/scans/projects:posture narrows one. Scope uses the SAME vocabulary projects:posture accepts — projects and include_archived — so the estate canvas narrows both reads with one control. Ids outside the caller's organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403. A SEPARATE endpoint from projects:posture, deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization's crypto data rather than its project count. Numbers here are the SUM of the per-project crypto rollups GET /v1/scans/projects/{projectId}/summary returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and crypto.projects carries the per-project values so a client can verify it by addition. See EstateCryptoAggregate for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition. Requires scans:read — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no crypto_not_entitled code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today. A trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.\",\"dateModified\":\"2026-10-07T10:42:12.813Z\",\"isPartOf\":{\"@id\":\"https://docs.scanoss.com#website\"},\"breadcrumb\":{\"@id\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects#breadcrumb\"}},{\"@type\":\"BreadcrumbList\",\"@id\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"API Reference\",\"item\":\"https://docs.scanoss.com/en/latest/earnie/api/using-the-api\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scans\",\"item\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-ai-provenance-posture-across-a-scope-of-projects\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"scans\",\"item\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-ai-provenance-posture-across-a-scope-of-projects\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"The organization's crypto posture across a scope of projects\",\"item\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects\"}]},{\"@type\":[\"TechArticle\",\"APIReference\"],\"@id\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects#apireference\",\"headline\":\"The organization's crypto posture across a scope of projects\",\"name\":\"The organization's crypto posture across a scope of projects\",\"description\":\"OMB M-23-02's federal PQC inventory is posed at exactly this altitude. Org-scoped by AUTHENTICATION, not by path. The organization is not a path parameter here because no route in this repo takes one: the organization is a per-deployment singleton and org scope is the tenant boundary resolved from the authenticated principal. A project-bound principal is narrowed to its own project, exactly as GET /v1/scans/projects:posture narrows one. Scope uses the SAME vocabulary projects:posture accepts — projects and include_archived — so the estate canvas narrows both reads with one control. Ids outside the caller's organization are dropped SILENTLY rather than rejected: scope is a view, and naming a project you cannot see should return an estate without it rather than leak that it exists through a 403. A SEPARATE endpoint from projects:posture, deliberately. This is the largest read on the projects surface — it reads every active crypto finding in scope — so the project table must not pay for it on every load. The cost is still a fixed number of queries: the findings for every in-scope project are read in ONE batched query and the aggregation is linear Go work, so the response cost tracks the organization's crypto data rather than its project count. Numbers here are the SUM of the per-project crypto rollups GET /v1/scans/projects/{projectId}/summary returns, computed by the same pure aggregator run once per project. That equality is a property of the construction, and crypto.projects carries the per-project values so a client can verify it by addition. See EstateCryptoAggregate for the inventory/outstanding-work line, the per-project asset-distinctness rule, and the one field that is NOT derivable by addition. Requires scans:read — the same permission the rest of the posture surface requires. There is deliberately NO crypto-specific 403 and no crypto_not_entitled code: an organization without the scanner reaches the ordinary absent response through the ordinary code path (no completed crypto stages, no crypto findings), byte-identical to an entitled organization that has never run crypto. A distinguishable refusal would advertise entitlement state on a read surface that carries none today. A trend at this altitude is deliberately absent: an arbitrary project scope has no history to recompute against. Crypto history is per-project and belongs to the scan-anchored surfaces.\",\"url\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects\",\"mainEntityOfPage\":{\"@id\":\"https://docs.scanoss.com/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects#webpage\"},\"dateModified\":\"2026-10-07T10:42:12.813Z\",\"publisher\":{\"@id\":\"https://docs.scanoss.com/#organization\"},\"isPartOf\":{\"@id\":\"https://docs.scanoss.com#website\"}}]}\u003c/script>\u003cscript data-mint-head type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"WebSite\",\"name\":\"SCANOSS documentation\",\"publisher\":{\"@type\":\"Organization\",\"name\":\"SCANOSS documentation\"},\"provider\":{\"@type\":\"Organization\",\"name\":\"Mintlify\",\"url\":\"https://mintlify.com\"}}\u003c/script>","agentPointerHref":"/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects.md","siteName":"SCANOSS documentation","nav":{"global":null,"versions":[{"version":"v2","default":true,"tabs":[{"tab":"Earnie","hidden":false,"groups":[{"group":"Get Started","expanded":false,"pages":[{"title":"What Is Earnie?","sidebarTitle":"What Is Earnie?","href":"/en/latest/earnie/introduction"},{"title":"Deployment Options and Data Flow","sidebarTitle":"Deployment and Data Flow","href":"/en/latest/earnie/deployment"},{"group":"Self-Hosting","expanded":false,"pages":[{"title":"Self-Hosting Requirements","sidebarTitle":"Self-Hosting Requirements","href":"/en/latest/earnie/self-hosting/self-hosting-requirements"},{"title":"Installing Earnie","sidebarTitle":"Installing Earnie","href":"/en/latest/earnie/self-hosting/installation"},{"title":"Running Earnie on a Cloud Provider","sidebarTitle":"Cloud Providers","href":"/en/latest/earnie/self-hosting/cloud-providers"},{"title":"Upgrading and Backing Up","sidebarTitle":"Upgrading and Backing Up","href":"/en/latest/earnie/self-hosting/upgrading-and-backups"},{"title":"Releases and Release Notes","sidebarTitle":"Releases","href":"/en/latest/earnie/self-hosting/releases"},{"title":"Outbound Network Calls","sidebarTitle":"Outbound Network Calls","href":"/en/latest/earnie/self-hosting/outbound-network-calls"}]},{"title":"Setting Up Your Workspace","sidebarTitle":"Workspace Setup","href":"/en/latest/earnie/getting-started/workspace-setup"},{"title":"Connecting a Repository","sidebarTitle":"Connecting a Repository","href":"/en/latest/earnie/getting-started/connecting-a-repository"},{"title":"Your First Scan","sidebarTitle":"First Scan","href":"/en/latest/earnie/getting-started/first-scan"}]},{"group":"Development","expanded":false,"pages":[{"title":"Earnie CLI","sidebarTitle":"Earnie CLI","href":"/en/latest/earnie/using-earnie/earnie-cli"},{"group":"Coding Agents (MCP)","expanded":false,"pages":[{"title":"Earnie MCP","sidebarTitle":"Overview","href":"/en/latest/earnie/mcp/overview"},{"title":"Connecting an AI Client","sidebarTitle":"Connecting a Client","href":"/en/latest/earnie/mcp/connecting-a-client"},{"title":"Using Earnie Through MCP","sidebarTitle":"Tools","href":"/en/latest/earnie/mcp/tools"},{"title":"Troubleshooting Earnie MCP","sidebarTitle":"Troubleshooting","href":"/en/latest/earnie/mcp/troubleshooting"}]},{"title":"Self-Checks","sidebarTitle":"Self-Checks","href":"/en/latest/earnie/using-earnie/self-checks"}]},{"group":"Pull Requests \u0026 CI","expanded":false,"pages":[{"title":"When the Gate Blocks a Merge","sidebarTitle":"Merge Gate","href":"/en/latest/earnie/using-earnie/merge-gate"},{"title":"Scan Configuration","sidebarTitle":"Scan Configuration","href":"/en/latest/earnie/using-earnie/scan-configuration"}]},{"group":"Governance","expanded":false,"pages":[{"title":"Reading the Dashboard","sidebarTitle":"Dashboard","href":"/en/latest/earnie/using-earnie/dashboard"},{"title":"Dependencies","sidebarTitle":"Dependencies","href":"/en/latest/earnie/using-earnie/dependencies"},{"title":"Vulnerability Statements (VEX)","sidebarTitle":"Vulnerabilities","href":"/en/latest/earnie/using-earnie/vulnerabilities"},{"title":"What a Project Uses, Reaches and Blocks","sidebarTitle":"Cryptography","href":"/en/latest/earnie/using-earnie/cryptography"},{"title":"Across Every Project","sidebarTitle":"All Projects","href":"/en/latest/earnie/using-earnie/all-projects"},{"title":"Triaging Findings","sidebarTitle":"Triaging Findings","href":"/en/latest/earnie/using-earnie/triaging-findings"},{"title":"Setting Your First Policy","sidebarTitle":"Setting Policies","href":"/en/latest/earnie/using-earnie/setting-policies"},{"title":"Notifications","sidebarTitle":"Notifications","href":"/en/latest/earnie/using-earnie/notifications"},{"title":"Language","sidebarTitle":"Language","href":"/en/latest/earnie/using-earnie/language"},{"group":"Domains","expanded":false,"pages":[{"title":"Cryptography","sidebarTitle":"Cryptography","href":"/en/latest/earnie/domains/cryptography"},{"title":"AI Provenance","sidebarTitle":"AI Provenance","href":"/en/latest/earnie/using-earnie/ai-provenance"}]}]},{"group":"Evidence \u0026 Audit","expanded":false,"pages":[{"title":"Exporting an SBOM","sidebarTitle":"Exporting SBOMs","href":"/en/latest/earnie/evidence/exporting-sboms"},{"title":"Reports","sidebarTitle":"Reports","href":"/en/latest/earnie/evidence/project-reports"},{"title":"Compliance Packages","sidebarTitle":"Compliance Packages","href":"/en/latest/earnie/evidence/compliance-packages"},{"title":"Audit Log","sidebarTitle":"Audit Log","href":"/en/latest/earnie/evidence/audit-log"}]},{"group":"Administration","expanded":false,"pages":[{"title":"Team and Roles","sidebarTitle":"Team \u0026 Roles","href":"/en/latest/earnie/administration/team-and-roles"},{"title":"API Keys","sidebarTitle":"API Keys","href":"/en/latest/earnie/administration/api-keys"}]},{"group":"Migrating","expanded":false,"pages":[{"title":"Migrating from SCANOSS Tools","sidebarTitle":"From SCANOSS Tools","href":"/en/latest/earnie/migrating/from-scanoss-tools"}]},{"group":"API Reference","expanded":false,"pages":[{"title":"Using the API","sidebarTitle":"Using the API","href":"/en/latest/earnie/api/using-the-api"},{"group":"Projects","pages":[{"group":"projects","pages":[{"title":"List projects for the authenticated organisation","deprecated":null,"version":null,"openapi":"/api-reference/earnie/projects-openapi.json get /v1/projects","href":"/earnie/api-reference/projects/projects/list-projects-for-the-authenticated-organisation"},{"title":"Create a new project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/projects-openapi.json post /v1/projects","href":"/earnie/api-reference/projects/projects/create-a-new-project"},{"title":"Get a project by ID","deprecated":null,"version":null,"openapi":"/api-reference/earnie/projects-openapi.json get /v1/projects/{projectId}","href":"/earnie/api-reference/projects/projects/get-a-project-by-id"},{"title":"Update a project's name or description","deprecated":null,"version":null,"openapi":"/api-reference/earnie/projects-openapi.json patch /v1/projects/{projectId}","href":"/earnie/api-reference/projects/projects/update-a-projects-name-or-description"},{"title":"Resolve one accessible project for a customer CLI","deprecated":null,"version":null,"openapi":"/api-reference/earnie/projects-openapi.json get /v1/projects:resolve","href":"/earnie/api-reference/projects/projects/resolve-one-accessible-project-for-a-customer-cli"}]}]},{"group":"Scans","pages":[{"group":"scans","pages":[{"title":"The organization's AI provenance posture across a scope of projects","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/ai/posture","href":"/earnie/api-reference/scans/scans/the-organizations-ai-provenance-posture-across-a-scope-of-projects"},{"title":"The curated rules Earnie assesses crypto findings against","description":"Returns the two curated datasets every crypto severity, post-quantum verdict and export signal is derived from: the risk tables and the export-control regime dataset. Severity provenance already travels with each finding, so a reader can see WHICH vintage judged it; this is what the rules of that vintage actually are.\n\nThe payload is projected from the same in-memory tables the scanner reads, so it cannot drift from the assessment it describes. It carries no tenant data and is identical for every organisation on a given binary — it changes only when the binary ships new datasets, which is why the response is safe to cache against its `ETag`.\n\nAccess is gated on the `crypto` scanner rather than on a permission slug: the payload is documentation about the product, and the curated algorithm vocabulary it publishes is the same dataset a non-entitled organisation is already withheld on `/v1/policies/fields/{path}/values`. Any authenticated principal of an entitled organisation may read it.\n\nEvery row states whether it is cited. Nothing here classifies anything: no ECCN is derived, printed or suggested, and FIPS 140-3 validation status is out of scope.","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/crypto/assessment-rules","href":"/earnie/api-reference/scans/scans/the-curated-rules-earnie-assesses-crypto-findings-against"},{"title":"The organization's crypto posture across a scope of projects","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/crypto/posture","href":"/earnie/api-reference/scans/scans/the-organizations-crypto-posture-across-a-scope-of-projects"},{"title":"Get the project's AI scanner settings","description":"A project that never saved them answers the defaults.","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/projects/{projectId}/ai-settings","href":"/earnie/api-reference/scans/scans/get-the-projects-ai-scanner-settings"},{"title":"Replace the project's AI scanner settings","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json put /v1/projects/{projectId}/ai-settings","href":"/earnie/api-reference/scans/scans/replace-the-projects-ai-scanner-settings"},{"title":"Crypto algorithms detected in one project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/projects/{projectId}/crypto-algorithms","href":"/earnie/api-reference/scans/scans/crypto-algorithms-detected-in-one-project"},{"title":"Dependency-internal crypto inventory for one component","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/projects/{projectId}/crypto-inventory","href":"/earnie/api-reference/scans/scans/dependency-internal-crypto-inventory-for-one-component"},{"title":"Declare a model upload, or resume the one in flight","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/projects/{projectId}/model-uploads","href":"/earnie/api-reference/scans/scans/declare-a-model-upload-or-resume-the-one-in-flight"},{"title":"Read an upload and its offset","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/projects/{projectId}/model-uploads/{uploadId}","href":"/earnie/api-reference/scans/scans/read-an-upload-and-its-offset"},{"title":"Send one window of an upload","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json put /v1/projects/{projectId}/model-uploads/{uploadId}","href":"/earnie/api-reference/scans/scans/send-one-window-of-an-upload"},{"title":"Abandon an upload","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json delete /v1/projects/{projectId}/model-uploads/{uploadId}","href":"/earnie/api-reference/scans/scans/abandon-an-upload"},{"title":"List the project's Models and its uploads in flight","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/projects/{projectId}/models","href":"/earnie/api-reference/scans/scans/list-the-projects-models-and-its-uploads-in-flight"},{"title":"Get one Model","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/projects/{projectId}/models/{modelId}","href":"/earnie/api-reference/scans/scans/get-one-model"},{"title":"Delete a Model","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json delete /v1/projects/{projectId}/models/{modelId}","href":"/earnie/api-reference/scans/scans/delete-a-model"},{"title":"List scans","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans","href":"/earnie/api-reference/scans/scans/list-scans"},{"title":"Upload a source archive and start a scan","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/scans","href":"/earnie/api-reference/scans/scans/upload-a-source-archive-and-start-a-scan"},{"title":"Get authoritative project scan summary","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/projects/{projectId}/state","href":"/earnie/api-reference/scans/scans/get-authoritative-project-scan-summary"},{"title":"Project posture rollup for the Audit landing","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/projects/{projectId}/summary","href":"/earnie/api-reference/scans/scans/project-posture-rollup-for-the-audit-landing"},{"title":"Project crypto posture rollup","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/projects/{projectId}/summary/crypto","href":"/earnie/api-reference/scans/scans/project-crypto-posture-rollup"},{"title":"Posture for every project in scope, in one response","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/projects:posture","href":"/earnie/api-reference/scans/scans/posture-for-every-project-in-scope-in-one-response"},{"title":"Get this deployment's upload limits","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/upload-limits","href":"/earnie/api-reference/scans/scans/get-this-deployments-upload-limits"},{"title":"Fetch a single scan by id","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}","href":"/earnie/api-reference/scans/scans/fetch-a-single-scan-by-id"},{"title":"Upload or resume a user-supplied archive object","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json put /v1/scans/{scanId}/archive","href":"/earnie/api-reference/scans/scans/upload-or-resume-a-user-supplied-archive-object"},{"title":"Read the upload offset of an archive object","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json head /v1/scans/{scanId}/archive","href":"/earnie/api-reference/scans/scans/read-the-upload-offset-of-an-archive-object"},{"title":"The Scan's Audit Trail","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}/audit","href":"/earnie/api-reference/scans/scans/the-scans-audit-trail"},{"title":"Compare crypto findings with another completed scan","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}/crypto/diff","href":"/earnie/api-reference/scans/scans/compare-crypto-findings-with-another-completed-scan"},{"title":"List all files in the scan (flat)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}/files","href":"/earnie/api-reference/scans/scans/list-all-files-in-the-scan-flat"},{"title":"Stream a single file's bytes from the retained archive","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}/files/content","href":"/earnie/api-reference/scans/scans/stream-a-single-files-bytes-from-the-retained-archive"},{"title":"Keep-set ingest cursor — received and missing paths","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}/ingest","href":"/earnie/api-reference/scans/scans/keep-set-ingest-cursor-—-received-and-missing-paths"},{"title":"Stream kept files as a tar","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json put /v1/scans/{scanId}/ingest","href":"/earnie/api-reference/scans/scans/stream-kept-files-as-a-tar"},{"title":"Match metadata + component + licenses for one file","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}/matches","href":"/earnie/api-reference/scans/scans/match-metadata-+-component-+-licenses-for-one-file"},{"title":"Proxy the bytes of an OSS file from the SCANOSS file-content service","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}/oss-files/content","href":"/earnie/api-reference/scans/scans/proxy-the-bytes-of-an-oss-file-from-the-scanoss-file-content-service"},{"title":"Per-scan rollup for the results-overview dashboard","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}/summary","href":"/earnie/api-reference/scans/scans/per-scan-rollup-for-the-results-overview-dashboard"},{"title":"Lazy folder expansion with aggregated state","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/scans/{scanId}/tree","href":"/earnie/api-reference/scans/scans/lazy-folder-expansion-with-aggregated-state"},{"title":"Cancel an in-progress scan","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/scans/{scanId}:cancel","href":"/earnie/api-reference/scans/scans/cancel-an-in-progress-scan"},{"title":"Seal the keep-set archive and start scanning","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/scans/{scanId}:commit-ingest","href":"/earnie/api-reference/scans/scans/seal-the-keep-set-archive-and-start-scanning"},{"title":"Explicitly rerun a scan","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/scans/{scanId}:rerun","href":"/earnie/api-reference/scans/scans/explicitly-rerun-a-scan"},{"title":"Retry a degraded provider publication","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/scans/{scanId}:retry-publication","href":"/earnie/api-reference/scans/scans/retry-a-degraded-provider-publication"},{"title":"Import a foreign SBOM document as a partial-coverage scan","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/scans:import-sbom","href":"/earnie/api-reference/scans/scans/import-a-foreign-sbom-document-as-a-partial-coverage-scan"},{"title":"Create a receiving scan for a resumable archive object","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/scans:plan-archive","href":"/earnie/api-reference/scans/scans/create-a-receiving-scan-for-a-resumable-archive-object"},{"title":"Plan a folder scan — keep engine then 202 receiving","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/scans:plan-folder","href":"/earnie/api-reference/scans/scans/plan-a-folder-scan-—-keep-engine-then-202-receiving"},{"title":"List Self-checks","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/self-checks","href":"/earnie/api-reference/scans/scans/list-self-checks"},{"title":"Run a Self-check over an inline SourceSet","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json post /v1/self-checks","href":"/earnie/api-reference/scans/scans/run-a-self-check-over-an-inline-sourceset"},{"title":"Get one Self-check","deprecated":null,"version":null,"openapi":"/api-reference/earnie/scans-openapi.json get /v1/self-checks/{selfCheckId}","href":"/earnie/api-reference/scans/scans/get-one-self-check"}]}]},{"group":"Findings","pages":[{"group":"audit","pages":[{"title":"List the durable audit-event trail for a subject (e.g. a finding)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/audit/events","href":"/earnie/api-reference/triage/audit/list-the-durable-audit-event-trail-for-a-subject-eg-a-finding"}]},{"group":"findings","pages":[{"title":"List findings with optional filters","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/findings","href":"/earnie/api-reference/triage/findings/list-findings-with-optional-filters"},{"title":"Create a new finding (source=api)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings","href":"/earnie/api-reference/triage/findings/create-a-new-finding-source=api"},{"title":"Bulk-reopen findings by component/path scope","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings/actions/bulk-reopen","href":"/earnie/api-reference/triage/findings/bulk-reopen-findings-by-componentpath-scope"},{"title":"Bulk-resolve open OSS findings by component/path scope","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings/actions/bulk-resolve","href":"/earnie/api-reference/triage/findings/bulk-resolve-open-oss-findings-by-componentpath-scope"},{"title":"Bulk-resolve open OSS findings across every project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings/actions/bulk-resolve-org-wide","href":"/earnie/api-reference/triage/findings/bulk-resolve-open-oss-findings-across-every-project"},{"title":"Count the open findings a bulk-resolve would affect","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings/actions/bulk-resolve-preview","href":"/earnie/api-reference/triage/findings/count-the-open-findings-a-bulk-resolve-would-affect"},{"title":"List findings aggregated by component (purl@version)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/findings/components","href":"/earnie/api-reference/triage/findings/list-findings-aggregated-by-component-purl@version"},{"title":"Membership Audit Trail for a component (base purl) selection","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/findings/components/audit-trail","href":"/earnie/api-reference/triage/findings/membership-audit-trail-for-a-component-base-purl-selection"},{"title":"List the filterable facet values a set of findings carries, with counts","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/findings/facets","href":"/earnie/api-reference/triage/findings/list-the-filterable-facet-values-a-set-of-findings-carries-with-counts"},{"title":"List findings aggregated by source file (review queue rows)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/findings/files","href":"/earnie/api-reference/triage/findings/list-findings-aggregated-by-source-file-review-queue-rows"},{"title":"Get a single finding by ID","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/findings/{findingId}","href":"/earnie/api-reference/triage/findings/get-a-single-finding-by-id"},{"title":"Assign a finding to an actor (also serves as defer/reassign)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings/{findingId}/actions/assign","href":"/earnie/api-reference/triage/findings/assign-a-finding-to-an-actor-also-serves-as-deferreassign"},{"title":"Create a configuration rule directly from a finding (mark-as-original)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings/{findingId}/actions/create-rule","href":"/earnie/api-reference/triage/findings/create-a-configuration-rule-directly-from-a-finding-mark-as-original"},{"title":"Reopen a resolved or assigned finding","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings/{findingId}/actions/reopen","href":"/earnie/api-reference/triage/findings/reopen-a-resolved-or-assigned-finding"},{"title":"Resolve a finding with a reason","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings/{findingId}/actions/resolve","href":"/earnie/api-reference/triage/findings/resolve-a-finding-with-a-reason"},{"title":"Suppress or unsuppress a finding (orthogonal to triage state)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/findings/{findingId}/actions/suppress","href":"/earnie/api-reference/triage/findings/suppress-or-unsuppress-a-finding-orthogonal-to-triage-state"},{"title":"Stream the dependency's resolved source for a crypto finding","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/findings/{findingId}/crypto-source","href":"/earnie/api-reference/triage/findings/stream-the-dependencys-resolved-source-for-a-crypto-finding"}]},{"group":"resolutions","pages":[{"title":"List resolutions (pending review queue)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/resolutions","href":"/earnie/api-reference/triage/resolutions/list-resolutions-pending-review-queue"},{"title":"Weekly decision throughput for a project, split by actor class","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json get /v1/resolutions/throughput","href":"/earnie/api-reference/triage/resolutions/weekly-decision-throughput-for-a-project-split-by-actor-class"},{"title":"Revert a pending_review resolution","deprecated":null,"version":null,"openapi":"/api-reference/earnie/triage-openapi.json post /v1/resolutions/{resolutionId}/actions/revert","href":"/earnie/api-reference/triage/resolutions/revert-a-pending_review-resolution"}]}]},{"group":"Policies","pages":[{"group":"policies","pages":[{"title":"List current policy verdicts for a finding","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/findings/{findingId}/policy-verdicts","href":"/earnie/api-reference/policies/policies/list-current-policy-verdicts-for-a-finding"},{"title":"List named regulatory policy template sets","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/policies/template-sets","href":"/earnie/api-reference/policies/policies/list-named-regulatory-policy-template-sets"},{"title":"List the projects a policy is attached to","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/policies/{id}/attachments","href":"/earnie/api-reference/policies/policies/list-the-projects-a-policy-is-attached-to"},{"title":"List (and page) policy approval history for a project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/projects/{projectId}/approvals","href":"/earnie/api-reference/policies/policies/list-and-page-policy-approval-history-for-a-project"},{"title":"List policies directly attached to a project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/projects/{projectId}/policies","href":"/earnie/api-reference/policies/policies/list-policies-directly-attached-to-a-project"},{"title":"Attach a policy directly to a project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json put /v1/projects/{projectId}/policies/{policyId}","href":"/earnie/api-reference/policies/policies/attach-a-policy-directly-to-a-project"},{"title":"Clone a policy attached (or attachable) to a project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json post /v1/projects/{projectId}/policies/{policyId}/clone","href":"/earnie/api-reference/policies/policies/clone-a-policy-attached-or-attachable-to-a-project"},{"title":"List immutable evaluation snapshots for an attached policy","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/projects/{projectId}/policies/{policyId}/evaluations","href":"/earnie/api-reference/policies/policies/list-immutable-evaluation-snapshots-for-an-attached-policy"},{"title":"List current findings violating an attached policy","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/projects/{projectId}/policies/{policyId}/violations","href":"/earnie/api-reference/policies/policies/list-current-findings-violating-an-attached-policy"},{"title":"Materialize an arbitrary, operator-chosen list of seeded templates","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json post /v1/projects/{projectId}/policies:from-templates","href":"/earnie/api-reference/policies/policies/materialize-an-arbitrary-operator-chosen-list-of-seeded-templates"},{"title":"Get the project's current policy posture","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/projects/{projectId}/policy-posture","href":"/earnie/api-reference/policies/policies/get-the-projects-current-policy-posture"},{"title":"Enable one named regulatory policy template set","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json post /v1/projects/{projectId}/policy-template-sets/{setSlug}:enable","href":"/earnie/api-reference/policies/policies/enable-one-named-regulatory-policy-template-set"},{"title":"Get the project's append-only posture time series","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/projects/{projectId}/posture-history","href":"/earnie/api-reference/policies/policies/get-the-projects-append-only-posture-time-series"},{"title":"What this scan was gated by","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/scans/{scanId}/policy-verdicts","href":"/earnie/api-reference/policies/policies/what-this-scan-was-gated-by"}]},{"group":"API Reference","pages":[{"title":"List policies","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/policies","href":"/earnie/api-reference/policies/list-policies"},{"title":"Create a policy","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json post /v1/policies","href":"/earnie/api-reference/policies/create-a-policy"},{"title":"Get the field catalog visible to the caller","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/policies/fields","href":"/earnie/api-reference/policies/get-the-field-catalog-visible-to-the-caller"},{"title":"Search values for an endpoint-sourced field","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/policies/fields/{path}/values","href":"/earnie/api-reference/policies/search-values-for-an-endpoint-sourced-field"},{"title":"List seeded policy templates","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/policies/templates","href":"/earnie/api-reference/policies/list-seeded-policy-templates"},{"title":"Read one policy","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json get /v1/policies/{id}","href":"/earnie/api-reference/policies/read-one-policy"},{"title":"Delete a policy","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json delete /v1/policies/{id}","href":"/earnie/api-reference/policies/delete-a-policy"},{"title":"Partial update of a policy","deprecated":null,"version":null,"openapi":"/api-reference/earnie/policies-openapi.json patch /v1/policies/{id}","href":"/earnie/api-reference/policies/partial-update-of-a-policy"}]}]},{"group":"SBOM","pages":[{"group":"sbom","pages":[{"title":"List a project's SBOM snapshots (newest first)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/sbom-openapi.json get /v1/sbom/projects/{projectId}/snapshots","href":"/earnie/api-reference/sbom/sbom/list-a-projects-sbom-snapshots-newest-first"},{"title":"Generate an SBOM snapshot from a scan","deprecated":null,"version":null,"openapi":"/api-reference/earnie/sbom-openapi.json post /v1/sbom/scans/{scanId}:generate","href":"/earnie/api-reference/sbom/sbom/generate-an-sbom-snapshot-from-a-scan"},{"title":"Fetch snapshot metadata","deprecated":null,"version":null,"openapi":"/api-reference/earnie/sbom-openapi.json get /v1/sbom/snapshots/{snapshotId}","href":"/earnie/api-reference/sbom/sbom/fetch-snapshot-metadata"},{"title":"Delete a snapshot (metadata + rendered artifacts + inventory)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/sbom-openapi.json delete /v1/sbom/snapshots/{snapshotId}","href":"/earnie/api-reference/sbom/sbom/delete-a-snapshot-metadata-+-rendered-artifacts-+-inventory"},{"title":"Download a rendered SBOM document (original bytes)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/sbom-openapi.json get /v1/sbom/snapshots/{snapshotId}/document","href":"/earnie/api-reference/sbom/sbom/download-a-rendered-sbom-document-original-bytes"},{"title":"Render an existing snapshot into another format","deprecated":null,"version":null,"openapi":"/api-reference/earnie/sbom-openapi.json post /v1/sbom/snapshots/{snapshotId}:render","href":"/earnie/api-reference/sbom/sbom/render-an-existing-snapshot-into-another-format"}]}]},{"group":"Estate Actions","pages":[{"group":"estate","pages":[{"title":"Poll a queued fan-out run","deprecated":null,"version":null,"openapi":"/api-reference/earnie/estate-openapi.json get /v1/estate/actions/{runId}","href":"/earnie/api-reference/estate/estate/poll-a-queued-fan-out-run"},{"title":"Attach a policy to every selected, eligible project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/estate-openapi.json post /v1/estate/projects:apply-policy","href":"/earnie/api-reference/estate/estate/attach-a-policy-to-every-selected-eligible-project"},{"title":"Generate an SBOM snapshot for every selected, eligible project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/estate-openapi.json post /v1/estate/projects:generate-sbom","href":"/earnie/api-reference/estate/estate/generate-an-sbom-snapshot-for-every-selected-eligible-project"},{"title":"Render a notice file for every selected, eligible project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/estate-openapi.json post /v1/estate/projects:render-notice","href":"/earnie/api-reference/estate/estate/render-a-notice-file-for-every-selected-eligible-project"},{"title":"Request a re-scan for every selected, eligible project","deprecated":null,"version":null,"openapi":"/api-reference/earnie/estate-openapi.json post /v1/estate/projects:request-scan","href":"/earnie/api-reference/estate/estate/request-a-re-scan-for-every-selected-eligible-project"}]}]},{"group":"Organization Settings","pages":[{"group":"organization","pages":[{"title":"Get organization profile","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json get /v1/organization","href":"/earnie/api-reference/platform/organization/get-organization-profile"},{"title":"Get the organization logo","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json get /v1/organization/branding/logo","href":"/earnie/api-reference/platform/organization/get-the-organization-logo"},{"title":"List the scanners enabled for your organization","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json get /v1/organization/modules","href":"/earnie/api-reference/platform/organization/list-the-scanners-enabled-for-your-organization"},{"title":"Get the organization's pull-request controls","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json get /v1/organization/pr-feedback","href":"/earnie/api-reference/platform/organization/get-the-organizations-pull-request-controls"},{"title":"Replace the organization's pull-request controls","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json put /v1/organization/pr-feedback","href":"/earnie/api-reference/platform/organization/replace-the-organizations-pull-request-controls"},{"title":"Get the organization's Scan Configuration","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json get /v1/organization/scan-configuration","href":"/earnie/api-reference/platform/organization/get-the-organizations-scan-configuration"},{"title":"Replace the organization's Scan Configuration","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json put /v1/organization/scan-configuration","href":"/earnie/api-reference/platform/organization/replace-the-organizations-scan-configuration"},{"title":"Get a project's auto-scan-on-merge setting","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json get /v1/projects/{projectId}/auto-scan","href":"/earnie/api-reference/platform/organization/get-a-projects-auto-scan-on-merge-setting"},{"title":"Enable or pause a project's auto-scan-on-merge","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json put /v1/projects/{projectId}/auto-scan","href":"/earnie/api-reference/platform/organization/enable-or-pause-a-projects-auto-scan-on-merge"},{"title":"Get a project's pre-commit hook setting","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json get /v1/projects/{projectId}/hook-settings","href":"/earnie/api-reference/platform/organization/get-a-projects-pre-commit-hook-setting"},{"title":"Set a project's pre-commit hook setting","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json put /v1/projects/{projectId}/hook-settings","href":"/earnie/api-reference/platform/organization/set-a-projects-pre-commit-hook-setting"},{"title":"Get a project's pull-request feedback setting","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json get /v1/projects/{projectId}/pr-feedback","href":"/earnie/api-reference/platform/organization/get-a-projects-pull-request-feedback-setting"},{"title":"Set a project's pull-request controls","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json put /v1/projects/{projectId}/pr-feedback","href":"/earnie/api-reference/platform/organization/set-a-projects-pull-request-controls"},{"title":"Get a project's Scan Configuration sources","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json get /v1/projects/{projectId}/scan-configuration","href":"/earnie/api-reference/platform/organization/get-a-projects-scan-configuration-sources"},{"title":"Replace a project's Scan Configuration","deprecated":null,"version":null,"openapi":"/api-reference/earnie/platform-openapi.json put /v1/projects/{projectId}/scan-configuration","href":"/earnie/api-reference/platform/organization/replace-a-projects-scan-configuration"}]}]},{"group":"Integrations","pages":[{"group":"integrations","pages":[{"title":"Each connection's recorded health, and their aggregate","deprecated":null,"version":null,"openapi":"/api-reference/earnie/integrations-openapi.json get /v1/integrations/connections","href":"/earnie/api-reference/integrations/integrations/each-connections-recorded-health-and-their-aggregate"},{"title":"GitHub connection status (liveness-checked)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/integrations-openapi.json get /v1/integrations/github","href":"/earnie/api-reference/integrations/integrations/github-connection-status-liveness-checked"},{"title":"List GitLab connections with what their tokens were checked to be","deprecated":null,"version":null,"openapi":"/api-reference/earnie/integrations-openapi.json get /v1/integrations/gitlab/connections","href":"/earnie/api-reference/integrations/integrations/list-gitlab-connections-with-what-their-tokens-were-checked-to-be"},{"title":"List the repositories the connections can access (live)","deprecated":null,"version":null,"openapi":"/api-reference/earnie/integrations-openapi.json get /v1/integrations/repositories","href":"/earnie/api-reference/integrations/integrations/list-the-repositories-the-connections-can-access-live"}]}]},{"group":"Components","pages":[{"group":"API Reference","pages":[{"title":"Search the SCANOSS component knowledgebase","deprecated":null,"version":null,"openapi":"/api-reference/earnie/components-openapi.json get /v1/components","href":"/earnie/api-reference/components/search-the-scanoss-component-knowledgebase"}]}]},{"group":"Audit log","pages":[{"group":"API Reference","pages":[{"title":"List instance-wide audit events","deprecated":null,"version":null,"openapi":"/api-reference/earnie/audit-openapi.json get /v1/audit-log","href":"/earnie/api-reference/audit/list-instance-wide-audit-events"},{"title":"Get one audit event","deprecated":null,"version":null,"openapi":"/api-reference/earnie/audit-openapi.json get /v1/audit-log/{eventId}","href":"/earnie/api-reference/audit/get-one-audit-event"}]}]}]}]},{"tab":"Developer Tools","hidden":false,"pages":[{"title":"Developer Tools","href":"/en/latest/developer-tools/overview"}]}]},{"version":"v1","pages":[{"title":"v1","href":"/en/latest/introduction/what-is-scanoss"}]}]},"basePath":"","title":"The organization's crypto posture across a scope of projects - SCANOSS documentation","buildId":"dpl_DqYu5MPb49gWBBbUGgpHQUmCHY3P","deploymentId":"dpl_DqYu5MPb49gWBBbUGgpHQUmCHY3P","dynamics":["10e4515597","c2aa737661","2b790eda92","b0f84f53ff","a9bb46feb3"],"chunks":["BannerMarkdown-DV3Oq1fY.js","dist-C-XZBk9h.js","lib-DuNMoZ05.js","lib-B8HbPgcC.js","clsx-D3Isdib3.js","html-void-elements-mCSPHezU.js","katex-YMM-FMeD.js","marked.esm-CZWythHk.js","OpenApiReferenceProvider-CybtLBIt.js","utils-BMLj2fvV.js","cloneDeep-izs3Hzxb.js","_Uint8Array-BVIqJ90l.js","isObjectLike-C8vmzPEN.js","isArray-Dcu1dQ5t.js","utils-B6In562Y.js","toString-BX-iyh8G.js","isSymbol-CSH9U2Gm.js","addUniqueKeysToSchema-Dr8Mfhp9.js","snippetPresets-2rmQvMVl.js","style-to-object-BY3JEAdk.js","v4-DIgz8zy6.js","conditional-requirements-CFM0id0Q.js","ApiExamples-WMqJYdZj.js","isEqual-BfaiBbcl.js","usePlaygroundInputsStore-CJ-MlPHu.js","shallow-dY3TMRCk.js","getApiPlaygroundDisplay-v-1B2bKm.js","CodeSnippet-BDhiTB7U.js","CodeSnippets-D9hnzQcS.js","Page-C4GwDT3_.js","getPastedJson-Th2V45jI.js","icon-BQXch1W9.js","MethodPill-BCqUneP3.js","DuplicateIcon-Q_-bhurZ.js","createIcon-DUjLHRqp.js","DynamicMarkdown-B-f2cqXQ.js","SectionHeading-Da5NsV4v.js","axios-vUo_bRtp.js","Markdown-D13FWkIM.js","AssistantPageLink--qIqmmVG.js"]}