-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Hello,
We consume MongoDB Java Driver artifacts from Maven Central and verify the OpenPGP signature of every POM we use before accepting it. Our policy only accepts a signature when the signing key's full fingerprint is confirmed by an official, public source of the publisher.
For the coordinates below we could not find such a source:
| Coordinate | Signature created (UTC) | Key algorithm | Hash algorithm | Issuer in signature |
|---|---|---|---|---|
| org.mongodb:mongodb-driver-bom:5.8.1 | 2026-07-16T17:27:30Z | RSA (1) | SHA-512 (10) | key ID 76E0008D166740A8 only |
Our request:
- A link to a public, permanent statement on your official website or official source repository (for example a KEYS file, a security page, or release documentation) that states the full 40-hex-character fingerprint of the OpenPGP key(s) used to sign the POM files you publish to Maven Central.
- In that statement, the scope of each key (which groupIds / artifacts it signs) and its validity period, or the dates of any key rotation, so that the signatures on the coordinates listed above can be matched to a specific key.
- If the key that signed any of the coordinates above is older or has been rotated: a public statement documenting the relationship between the old and the new fingerprint (for example a transition statement signed by both keys), or, if that is not possible, a newly published signature for the affected release made with the current, documented key.
- Context: the page https://www.mongodb.com/docs/drivers/java/sync/current/security/validate-signatures/ shows the key ID 76E0008D166740A8 and the fingerprint 1A75005E142192223D6A7C3B76E0008D166740A8, but only inside an example of verification output for mongodb-driver-core 5.1.0. We do not treat example output as a key statement. We would ask for an explicit, permanent statement of the signing key's full fingerprint and its scope for the Java driver artifacts, including mongodb-driver-bom:5.8.1.
What we can and cannot accept as evidence
- We can only rely on a statement published in an official, public channel of the project (website, official repository file, release notes, or a public issue/discussion answered by a maintainer and then reflected in a permanent page).
- A private reply or an unpublished message cannot be used as evidence. If you answer privately, we would kindly ask you to publish the same confirmation publicly.
- A key retrieved from a public keyserver, or a fingerprint shown only in an example of verification output, is not treated by us as a statement issued by the publisher.
Thank you for your time and for maintaining this project.
Kind regards,
MOUFLEH ABDELJAWAD - AGBHub
Generated by Claude Code