Add Insights Documentation and Spec - #101
Conversation
Signed-off-by: Steve Springett <steve@springett.us>
|
Looks good. Will the spec provide the data model too? |
|
Yes it will provide the data model. That's the next thing I need to work on. I need to completely refactor the CycloneDX API schema by modularization it and fixing some of the small things we want to break in 2.0. |
|
hey @stevespringett i'm currently using this for my implementation and will do some conformance testing and leave feedback on what that reveals |
OWASP Transparency Exchange API — conformance and performance report
Result
PerformanceCold start: 367 ms. That is the first request against a tenant whose object Each row replays one request shape 100 times at 32 in flight. Every response was
Insights API
Queries exercised
Conformance-phase latencyThe distribution across all 160 conformance cases — one request each, including the
EfficacyConformance proves the responses are well-formed. It cannot prove they are complete —
Published artifact types
Published documents
Artifact revision depthHow many immutable revisions each published artifact has. Depth beyond 1 is TEA's
Coverage by operation
Discovery document
Coverage by case category
FixturesThe run walked the object graph from
MethodEvery response was validated client-side against the schema the specification Assertions the schemas cannot express — collection/release UUID identity, CLE event |

No description provided.