How standard libraries read PEM files

1 PEM file given to 4 readers in 14 runtime versions. Cells of the ordinary files: reads 14, differs 0, refuses 0, crashes 0. How this is measured. The results as JSON.

PEM files, by reader
FileThe manifest says Go crypto/x509 adapter Java java.security.cert.CertificateFactory adapter Node.js crypto.X509Certificate adapter Ruby OpenSSL::X509::Certificate adapter Python
The standard library has no certificate parser: ssl loads certificates for TLS and offers none that returns a subject, an issuer, a serial and names.
pem/self-signed-ed25519-cert.pem 542 B dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example

reads reports dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example

reads reports dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example

reads reports dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example

reads reports dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example

no-reader

The PEM files themselves, and the measured properties each row is compared with: PEM sample files.