ProgressLive from the pipelines
Measured, not claimed.
Every figure on this page is posted by a build pipeline on develop or main, signed by the job that produced it, and kept with the commit it measured. Nothing is typed in by hand, and the page reads them again every minute.
Standards
Each normative clause of each registered specification, linked to the code that implements it and the test that proves it.
Requirements, cited and tested.
aegis-platform
updated from aegis-platform@01d43f9
- Documents
- 146
- Mandatory
- 7,699
- Cited
- 1,878
- Tested
- 922
| Document | Mandatory | Cited | Tested |
|---|---|---|---|
| OpenID Federation 1.0OPENID-FEDERATION-1.0 | 469 | 0 | 0 |
| The Transport Layer Security (TLS) Protocol Version 1.3RFC9846 | 353 | 0 | 0 |
| The Transport Layer Security (TLS) Protocol Version 1.3RFC8446 | 340 | 0 | 0 |
| OpenID Federation 1.1OPENID-FEDERATION-1.1 | 336 | 0 | 0 |
| Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileRFC5280 | 313 | 130 | 38 |
| OpenID Connect Core 1.0 incorporating errata set 2OIDC-CORE-1.0 | 303 | 117 | 8 |
| OpenID for Verifiable Credential Issuance 1.0OPENID4VCI-1.0 | 277 | 243 | 171 |
| OpenID for Verifiable Presentations 1.0OPENID4VP-1.0 | 267 | 204 | 88 |
| The OAuth 2.1 Authorization FrameworkDRAFT-IETF-OAUTH-V2-1-16 | 205 | 0 | 0 |
| HTTP SemanticsRFC9110 | 202 | 17 | 5 |
| Tags for Identifying LanguagesRFC5646 | 170 | 93 | 0 |
| The OAuth 2.0 Authorization FrameworkRFC6749 | 159 | 84 | 62 |
| Decentralized Identifiers (DIDs) v1.0W3C-DID-CORE-1.0 | 139 | 0 | 0 |
| DIDComm Messaging v2.0DIDCOMM-2.0 | 138 | 47 | 1 |
| DIDComm Messaging v2.1DIDCOMM-2.1 | 136 | 0 | 0 |
| JSON-LD 1.1W3C-JSON-LD-1.1 | 125 | 0 | 0 |
| SD-JWT-based Verifiable Digital Credentials (SD-JWT VC)DRAFT-IETF-OAUTH-SD-JWT-VC-19 | 119 | 88 | 66 |
| Decentralized Identifier Resolution (DID Resolution) v1.0W3C-DID-RESOLUTION-1.0 | 96 | 0 | 0 |
| Selective Disclosure for JSON Web TokensRFC9901 | 96 | 70 | 56 |
| Verifiable Credentials Data Model v2.0W3C-VC-DATA-MODEL-2.0 | 95 | 34 | 14 |
| CBOR Object Signing and Encryption (COSE): Initial AlgorithmsRFC9053 | 94 | 17 | 5 |
| Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)RFC6125 | 92 | 0 | 0 |
| Token Status List (TSL)DRAFT-IETF-OAUTH-STATUS-LIST-21 | 92 | 85 | 77 |
| OAuth 2.0 Attestation-Based Client AuthenticationDRAFT-IETF-OAUTH-ATTESTATION-BASED-CLIENT-AUTH-11 | 90 | 70 | 39 |
| Certificate Transparency Version 2.0RFC9162 | 89 | 0 | 0 |
| OpenID4VC High Assurance Interoperability Profile 1.0HAIP-1.0 | 86 | 59 | 51 |
| Token Status List (TSL)DRAFT-IETF-OAUTH-STATUS-LIST-15 | 83 | 0 | 0 |
| Controlled Identifiers v1.0W3C-CID-1.0 | 80 | 0 | 0 |
| Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileRFC4055 | 69 | 2 | 0 |
| Verifiable Credentials Data Model v1.1W3C-VC-DATA-MODEL-1.1 | 68 | 0 | 0 |
| HTTP CachingRFC9111 | 64 | 0 | 0 |
| Best Current Practice for OAuth 2.0 SecurityRFC9700 | 63 | 2 | 0 |
| FAPI 2.0 Security ProfileFAPI-2.0-SP | 63 | 0 | 0 |
| JSON Web Signature (JWS)RFC7515 | 60 | 41 | 16 |
| Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)RFC3161 | 59 | 1 | 0 |
| The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)RFC9101 | 59 | 19 | 0 |
| Verifiable Credential Data Integrity 1.0W3C-VC-DATA-INTEGRITY-1.0 | 59 | 16 | 0 |
| JSON Web Algorithms (JWA)RFC7518 | 58 | 25 | 10 |
| Cryptographic Message Syntax (CMS) AlgorithmsRFC3370 | 55 | 4 | 4 |
| OpenID Connect Discovery 1.0 incorporating errata set 2OIDC-DISCOVERY-1.0 | 55 | 25 | 0 |
| Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)RFC9325 | 52 | 0 | 0 |
| Decentralized Identifiers (DIDs) v1.1W3C-DID-CORE-1.1 | 51 | 0 | 0 |
| Securing Verifiable Credentials using JOSE and COSEW3C-VC-JOSE-COSE-1.0 | 50 | 0 | 0 |
| Data Integrity ECDSA Cryptosuites v1.0W3C-VC-DI-ECDSA-1.0 | 47 | 15 | 1 |
| Data Integrity EdDSA Cryptosuites v1.0W3C-VC-DI-EDDSA-1.0 | 47 | 12 | 1 |
| X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSPRFC6960 | 45 | 26 | 20 |
| OAuth 2.0 Demonstrating Proof of Possession (DPoP)RFC9449 | 44 | 31 | 22 |
| OAuth 2.0 Dynamic Client Registration Management ProtocolRFC7592 | 44 | 0 | 0 |
| Internet X.509 Public Key Infrastructure: Qualified Certificates ProfileRFC3739 | 43 | 7 | 0 |
| Bitstring Status List v1.0W3C-BITSTRING-STATUS-LIST-1.0 | 42 | 33 | 15 |
| Trace ContextW3C-TRACE-CONTEXT | 42 | 0 | 0 |
| Hybrid Public Key EncryptionRFC9180 | 41 | 0 | 0 |
| Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileRFC3279 | 39 | 6 | 0 |
| CBOR Object Signing and Encryption (COSE): Structures and ProcessRFC9052 | 39 | 3 | 0 |
| OAuth 2.0 Dynamic Client Registration ProtocolRFC7591 | 39 | 0 | 0 |
| OpenID Connect for Identity Assurance 1.0OIDC4IDA-1.0 | 39 | 0 | 0 |
| WebFingerRFC7033 | 39 | 0 | 0 |
| JSON Web Encryption (JWE)RFC7516 | 38 | 6 | 5 |
| OAuth 2.0 Authorization Server MetadataRFC8414 | 35 | 21 | 13 |
| Service Identity in TLSRFC9525 | 35 | 0 | 0 |
| New ASN.1 Modules for the Public Key Infrastructure Using X.509 (PKIX)RFC5912 | 34 | 0 | 0 |
| OAuth 2.0 for Browser-Based ApplicationsRFC10017 | 34 | 0 | 0 |
| The OAuth 2.0 Authorization Framework: Bearer Token UsageRFC6750 | 34 | 11 | 10 |
| JSON Web Key (JWK)RFC7517 | 30 | 8 | 3 |
| JSON Canonicalization Scheme (JCS)RFC8785 | 29 | 22 | 16 |
| JSON-LD 1.1 Processing Algorithms and APIW3C-JSON-LD-API-1.1 | 29 | 0 | 0 |
| OAuth 2.0 Protected Resource MetadataRFC9728 | 29 | 0 | 0 |
| JSON Web Token (JWT) Profile for OAuth 2.0 Access TokensRFC9068 | 28 | 0 | 0 |
| Universally Unique IDentifiers (UUIDs)RFC9562 | 28 | 2 | 0 |
| Concise Binary Object Representation (CBOR)RFC8949 | 26 | 16 | 11 |
| JSON Web Token (JWT)RFC7519 | 26 | 12 | 0 |
| Web LinkingRFC8288 | 26 | 0 | 0 |
| Assertion Framework for OAuth 2.0 Client Authentication and Authorization GrantsRFC7521 | 25 | 0 | 0 |
| Uniform Resource Names (URNs)RFC8141 | 25 | 0 | 0 |
| JSON Web Token Best Current PracticesRFC8725 | 24 | 8 | 8 |
| Internationalized Resource Identifiers (IRIs)RFC3987 | 23 | 0 | 0 |
| OAuth 2.0 Authorization Server Issuer IdentificationRFC9207 | 21 | 14 | 14 |
| OAuth 2.0 Device Authorization GrantRFC8628 | 21 | 0 | 0 |
| AnonCreds SpecificationANONCREDS-1.0 | 20 | 12 | 8 |
| OAuth 2.0 Token IntrospectionRFC7662 | 20 | 0 | 0 |
| Aries RFC 0434: Out-of-Band Protocol 1.1ARIES-RFC-0434 | 19 | 6 | 3 |
| Deprecating TLS 1.0 and TLS 1.1RFC8996 | 19 | 0 | 0 |
| Elliptic Curve Cryptography Subject Public Key InformationRFC5480 | 19 | 9 | 0 |
| JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization GrantsRFC7523 | 19 | 15 | 1 |
| The did:key Method v0.9DID-KEY | 18 | 0 | 0 |
| JSON-LD 1.1 FramingW3C-JSON-LD-FRAMING-1.1 | 17 | 0 | 0 |
| OAuth 2.0 Pushed Authorization RequestsRFC9126 | 17 | 15 | 13 |
| OAuth 2.0 Token ExchangeRFC8693 | 17 | 0 | 0 |
| Lightweight Directory Access Protocol (LDAP): Schema for User ApplicationsRFC4519 | 16 | 0 | 0 |
| OAuth 2.0 for Native AppsRFC8252 | 16 | 1 | 0 |
| Permissions PolicyW3C-PERMISSIONS-POLICY-1 | 15 | 0 | 0 |
| RDF Dataset Canonicalization (RDFC-1.0)W3C-RDF-CANON-1.0 | 15 | 0 | 0 |
| IPv6 Addressing of IPv4/IPv6 TranslatorsRFC6052 | 14 | 0 | 0 |
| CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 CertificatesRFC9360 | 13 | 10 | 10 |
| Matching of Language TagsRFC4647 | 13 | 0 | 0 |
| Online Certificate Status Protocol Algorithm AgilityRFC6277 | 13 | 0 | 0 |
| OAuth 2.0 Rich Authorization RequestsRFC9396 | 12 | 3 | 2 |
| Proof Key for Code Exchange by OAuth Public ClientsRFC7636 | 12 | 10 | 6 |
| OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensRFC8705 | 11 | 0 | 0 |
| OAuth 2.0 Token RevocationRFC7009 | 11 | 0 | 0 |
| Digital Credentials APIW3C-DIGITAL-CREDENTIALS | 10 | 1 | 1 |
| Forwarded HTTP ExtensionRFC7239 | 10 | 5 | 0 |
| JSON Web Signature (JWS) Unencoded Payload OptionRFC7797 | 10 | 0 | 0 |
| Key words for use in RFCs to Indicate Requirement LevelsRFC2119 | 10 | 0 | 0 |
| Using SHA2 Algorithms with Cryptographic Message SyntaxRFC5754 | 10 | 5 | 5 |
| Aries RFC 0023: DID Exchange v1ARIES-RFC-0023 | 9 | 0 | 0 |
| CBOR Web Token (CWT)RFC8392 | 9 | 0 | 0 |
| did:web Method SpecificationDID-WEB | 9 | 0 | 0 |
| Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSARFC5758 | 9 | 5 | 0 |
| Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)RFC7800 | 9 | 4 | 2 |
| The Base16, Base32, and Base64 Data EncodingsRFC4648 | 9 | 0 | 0 |
| CFRG Elliptic Curve Diffie-Hellman (ECDH) and Signatures in JSON Object Signing and Encryption (JOSE)RFC8037 | 8 | 6 | 6 |
| Handling Long Lines in Content of Internet-Drafts and RFCsRFC8792 | 8 | 0 | 0 |
| Special-Use Domain NamesRFC6761 | 8 | 2 | 1 |
| The JavaScript Object Notation (JSON) Data Interchange FormatRFC8259 | 7 | 1 | 0 |
| Aries RFC 0094: Cross-Domain MessagingARIES-RFC-0094 | 6 | 0 | 0 |
| PATCH Method for HTTPRFC5789 | 6 | 0 | 0 |
| Problem Details for HTTP APIsRFC9457 | 6 | 2 | 2 |
| The Web Origin ConceptRFC6454 | 6 | 0 | 0 |
| Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key InfrastructureRFC8410 | 5 | 2 | 0 |
| Aries RFC 0348: Transition Message Type to HTTPsARIES-RFC-0348 | 5 | 0 | 0 |
| New Protocols Using TLS Must Require TLS 1.3RFC9852 | 5 | 0 | 0 |
| Online Certificate Status Protocol (OCSP) Nonce ExtensionRFC9654 | 5 | 5 | 5 |
| The I-JSON Message FormatRFC7493 | 5 | 0 | 0 |
| An IETF URN Sub-namespace for Registered Protocol ParametersRFC3553 | 4 | 0 | 0 |
| Aries RFC 0044: DIDComm File and MIME TypesARIES-RFC-0044 | 4 | 1 | 0 |
| Date and Time on the Internet: TimestampsRFC3339 | 4 | 0 | 0 |
| JSON Web Key (JWK) ThumbprintRFC7638 | 4 | 4 | 4 |
| AnonCreds Methods RegistryANONCREDS-METHODS-REGISTRY | 3 | 0 | 0 |
| Aries RFC 0003: ProtocolsARIES-RFC-0003 | 3 | 2 | 0 |
| Aries RFC 0017: AttachmentsARIES-RFC-0017 | 3 | 0 | 0 |
| Aries RFC 0771: AnonCreds Attachment Formats for Requesting and Presenting CredentialsARIES-RFC-0771 | 3 | 2 | 0 |
| Asymmetric Key PackagesRFC5958 | 3 | 0 | 0 |
| The "xml2rfc" Version 3 VocabularyRFC7991 | 3 | 0 | 0 |
| Well-Known Uniform Resource Identifiers (URIs)RFC8615 | 3 | 0 | 0 |
| Aries RFC 0592: Indy Attachment Formats for Requesting and Presenting CredentialsARIES-RFC-0592 | 2 | 0 | 0 |
| Resource Indicators for OAuth 2.0RFC8707 | 2 | 2 | 2 |
| Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsRFC8174 | 1 | 0 | 0 |
| Aries RFC 0008: Message ID and ThreadingARIES-RFC-0008 | 1 | 1 | 0 |
| Aries RFC 0019: Encryption EnvelopeARIES-RFC-0019 | 1 | 0 | 0 |
| Aries RFC 0035: Report Problem Protocol 1.0ARIES-RFC-0035 | 1 | 0 | 0 |
| Aries RFC 0048: Trust Ping Protocol 1.0ARIES-RFC-0048 | 1 | 0 | 0 |
| Aries RFC 0160: Connection ProtocolARIES-RFC-0160 | 1 | 0 | 0 |
| Aries RFC 0453: Issue Credential Protocol 2.0ARIES-RFC-0453 | 1 | 1 | 1 |
| CBOR Object Signing and Encryption (COSE) "typ" (type) Header ParameterRFC9596 | 1 | 0 | 0 |
| Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data StructuresRFC8610 | 1 | 0 | 0 |
Tests
Every suite in each repository, as its last build on develop or main ran it.
Every suite, every repository.
aegis-platform
updated from aegis-platform@01d43f9
- Suites
- 1
- Passed
- 6,399
- Failed
- 0
- Skipped
- 0
| Suite | Passed | Failed | Skipped |
|---|---|---|---|
| aegis-platform · frontend · vitest | 6,399 | 0 | 0 |
protoworks-defence-ssi
updated from protoworks-defence-ssi@f4c0c85
- Suites
- 1
- Passed
- 4,294
- Failed
- 0
- Skipped
- 0
| Suite | Passed | Failed | Skipped |
|---|---|---|---|
| protoworks-defence-ssi · cargo nextest --all-features | 4,294 | 0 | 0 |
Conformance
Runs against the published conformance suites. Expected failures are the checks a plan marks as not applying.
Held to the published suites.
protoworks-defence-ssi
updated from protoworks-defence-ssi@f4c0c85
- Runs
- 32
- Passed
- 1,946 of 1,997
- Expected failures
- 37
| Suite | Plan | Passed | Expected failures |
|---|---|---|---|
| OpenID Foundation conformance suite 5.3.2 | oidcc-client-basic-certification-test-plan (client_registration=static_client, request_type=plain_http_request) | 13 / 14 | 0 |
| OpenID Foundation conformance suite 5.3.2 | oidcc-client-config-certification-test-plan (client_registration=static_client, client_auth_type=client_secret_basic, request_type=plain_http_request, response_mode=default) | 5 / 6 | 0 |
| OpenID Foundation conformance suite 5.3.2 | oidcc-client-formpost-basic-certification-test-plan (client_registration=static_client, request_type=plain_http_request) | 13 / 14 | 0 |
| OpenID Foundation conformance suite 5.3.2 | oidcc-client-test-plan (client_registration=static_client, response_type=code, client_auth_type=client_secret_post, request_type=plain_http_request, response_mode=default) | 28 / 29 | 0 |
| OpenID Foundation conformance suite 5.3.2 | oidcc-client-test-plan (client_registration=static_client, response_type=code, client_auth_type=private_key_jwt, request_type=request_object, response_mode=default) | 27 / 28 | 0 |
| OpenID Foundation conformance suite 5.3.2 | oidcc-client-test-plan (client_registration=static_client, response_type=code, client_auth_type=client_secret_jwt, request_type=request_uri, response_mode=form_post) | 30 / 32 | 1 |
| OpenID Foundation conformance suite 5.3.2 | oidcc-client-test-plan (client_registration=static_client, response_type=code, client_auth_type=tls_client_auth, request_type=plain_http_request, response_mode=default) | 28 / 29 | 0 |
| Aries Agent Test Harness (owl-agent-test-harness 62f2ddd) against ACA-Py 1.7.0 | acme: ptwd as Acme (requester, inviter) | 18 / 18 | 0 |
| Aries Agent Test Harness (owl-agent-test-harness 62f2ddd) against ACA-Py 1.7.0 | bob: ptwd as Bob (responder, invitee) | 18 / 18 | 0 |
| Aries Agent Test Harness (owl-agent-test-harness 62f2ddd) against ACA-Py 1.7.0 | pair: ptwd in every role | 16 / 27 | 11 |
| Aries Agent Test Harness (owl-agent-test-harness 62f2ddd) against ACA-Py 1.7.0 | cred-acme-indy: ptwd as Acme (issuer), Indy | 4 / 7 | 3 |
| Aries Agent Test Harness (owl-agent-test-harness 62f2ddd) against ACA-Py 1.7.0 | cred-bob-indy: ptwd as Bob (holder, prover), Indy | 4 / 7 | 3 |
| Aries Agent Test Harness (owl-agent-test-harness 62f2ddd) against ACA-Py 1.7.0 | cred-faber-indy: ptwd as Faber (verifier), Indy | 4 / 7 | 3 |
| Aries Agent Test Harness (owl-agent-test-harness 62f2ddd) against ACA-Py 1.7.0 | cred-acme-anoncreds: ptwd as Acme (issuer), AnonCreds | 4 / 7 | 3 |
| Aries Agent Test Harness (owl-agent-test-harness 62f2ddd) against ACA-Py 1.7.0 | cred-bob-anoncreds: ptwd as Bob (holder, prover), AnonCreds | 4 / 7 | 3 |
| didwebvh-test-suite (703f97f), every implementation's vectors | ptwd-did-webvh as the resolver (PASS and SPEC; SKIP excluded) | 113 / 113 | 0 |
| W3C JSON-LD 1.1 API test suite (w3c/json-ld-api 55514738) | expand (applicable cases) | 377 / 377 | 0 |
| W3C JSON-LD 1.1 API test suite (w3c/json-ld-api 55514738) | compact (applicable cases) | 244 / 244 | 0 |
| W3C JSON-LD 1.1 API test suite (w3c/json-ld-api 55514738) | flatten (applicable cases) | 55 / 55 | 0 |
| W3C JSON-LD 1.1 API test suite (w3c/json-ld-api 55514738) | toRdf (applicable cases) | 456 / 456 | 0 |
| W3C JSON-LD 1.1 API test suite (w3c/json-ld-api 55514738) | fromRdf (applicable cases) | 53 / 53 | 0 |
| W3C RDF Dataset Canonicalization test suite (w3c/rdf-canon 15619df2) | RDFC-1.0 | 86 / 86 | 0 |
| W3C RDF 1.1 N-Quads test suite (2014-02-18) | N-Quads syntax | 85 / 85 | 0 |
| Differential: ptwd-oidc-rp against openidconnect 4.0.1 and jsonwebtoken 11.1.0 | OpenID Connect Core 1.0 and Discovery 1.0 rows (disagreements are ptwd-oidc-rp's stricter checks) | 32 / 39 | 7 |
| OpenID Foundation conformance suite 5.3.2 | oid4vp-1final-verifier-haip-test-plan (credential_format=sd_jwt_vc, response_mode=direct_post.jwt): 7 PASSED, 3 REVIEW verified, 1 SKIPPED | 10 / 11 | 0 |
| OpenID Foundation conformance suite 5.3.2 | openid-federation-deployed-entity-test-plan (alpha): five entities over ptwd-openid-federation | 13 / 20 | 1 |
| cose-wg/Examples (53c9d63), COSE_Sign1 | ptwd-token-status-list's statuslist+cwt envelope: every case decided as it intends | 15 / 15 | 0 |
| ToIP TRQP v2.0 wire suite (ours: no formal TRQP suite exists) | ptwd-trqp, every MUST observable on the wire | 15 / 15 | 0 |
| W3C VC test suites through the VC-API shim | VCDM 2.0 (vc-data-model-2.0-test-suite 62836458) | 58 / 59 | 1 |
| W3C VC test suites through the VC-API shim | Data Integrity eddsa-rdfc-2022 (vc-di-eddsa-test-suite 1e86cc4c) | 43 / 44 | 1 |
| W3C VC test suites through the VC-API shim | Data Integrity ecdsa-rdfc-2019, P-256 and P-384 (vc-di-ecdsa-test-suite 94dca21d; pending excluded) | 57 / 57 | 0 |
| W3C VC test suites through the VC-API shim | Bitstring Status List (vc-bitstring-status-list-test-suite 960ab9a3; pending excluded) | 18 / 18 | 0 |
Certification
The programmes and registrations the platform is working through, and where each one stands.
Where each programme stands.
No certification report has arrived yet; it appears here when its pipeline first posts one.
Build on identity that is proven, not assumed.
Aegis is built by Protoworks and offered to partners on request. Tell us what you need to verify, issue or accept, and we will show you the platform running.