Who Actually Publishes a COA Library
ON THIS PAGE
Key findings
- 50 of the 126 supplier records in this publication's ledger, read 2026-09-19, mention a certificate library or index by name, a substring search for the words library or index appearing near certificate or COA language. The count describes what the ledger's own text records, not whether the library found there is complete or current.
- Genesis Peptides routes every product page it publishes to one shared destination, a library whose own header states "141 Peptide Certificates of Analysis," rather than linking a certificate from each product page individually, read 2026-08-20.
- Koi Peptides Canada's own COA library, read 2026-08-26, lists 32 documents indexed by compound and lot. A separate check of the issuing laboratory's own portal the same day turned up 14 additional, more recently dated search codes that do not appear anywhere on the vendor's library page.
A certificate library is a specific structural claim, not just a promise that documentation exists somewhere. It says one address holds many certificates, organized and browsable, rather than one document scattered per product page or nothing published at all. This ledger shows what that specific claim looks like once someone actually opens the page behind it.
How many claim one at all
50 of the 126 supplier records in this publication's ledger, read 2026-09-19, mention a certificate library or index by name. The search behind that count is a substring search for the words library or index appearing near certificate or COA language, run directly against this publication's own ledger. It is not a judgment about whether the library any of those 50 records describes is complete, current, or organized in a way a visitor would actually call browsable; it counts only whether the ledger's own text uses that vocabulary at all. A looser or stricter search would return a different number, and the two cases below show why the word alone settles very little.
A library that states its own size
Genesis Peptides' catalog, read 2026-08-20, does not link an individual certificate from each product page. Every product page this publication opened, spanning several different compounds, routes instead to one shared destination labeled "View COA Library." That page's own header states its scope in a specific number: "141 Peptide Certificates of Analysis." Whatever else a reader might want to check about those 141 documents, the library at least states plainly how many certificates it holds, on its own page, rather than leaving a visitor to count.
A library missing what the lab already has
Koi Peptides Canada's own COA library, read 2026-08-26, lists 32 documents indexed by compound, lot number, purity figure, and test date, each with a linked file. A separate check of the issuing laboratory's own portal the same day, run independently of the vendor's own page, turned up a further 14 search codes, dated June 2026, more recent than several of the documents the vendor's own library shows. None of those 14 codes appears anywhere on the vendor's own library page. The laboratory has already issued and can already confirm documents this specific library does not yet show, which means the library's own count, 32, undercounts what is checkable through the lab directly, on the same date this ledger read both.
What the word library does not establish
Neither of the two cases above is a library that does not exist. Each is a real, checkable page a visitor can open. What neither of them establishes, just by existing, is that the certificates inside are complete relative to what the issuing laboratory actually holds. A library is the structural precondition for that check, the thing that has to exist before a reader can compare it against the laboratory's own records at all. It is not, on its own, proof that the comparison would come out clean.
Limitations and open questions
This piece describes two dated cases, read 2026-08-20 and 2026-08-26, and a vendor's library page, or the laboratory portal checked against it, can change at any time after those dates. The 50-record count is a substring search over this publication's own ledger, run 2026-09-19, for the words library or index near certificate or COA language, and describes what this publication's dossiers recorded rather than a market-wide count of every seller running something a visitor would call a library. This piece takes no position on why Koi Peptides Canada's library has not caught up to the laboratory's own more recent codes; it reports what each page states, not a finding about intent behind the gap.
A library is a page a reader can actually check. Whether it holds up once checked is a separate question, and each of these two cases answers it differently.
Sources
Supplier observations are this publication's own, from the dossier record in ledger/vendors.json: Genesis Peptides, read 2026-08-20; Koi Peptides Canada, read 2026-08-26. The 50-record count was run directly against ledger/vendors.json on 2026-09-19. Vendors are named here, never linked, per site policy.
Email updates
New articles and news by email, at most once a day or once a week, whichever you pick.
Respond to this analysis
Corrections, contradictions, and anything you have seen yourself. Responses are read and checked. Verified ones become entries in the ledger or corrections to this page. Nothing posts unverified, and no response is published with anything but the handle you type, or the display name of the account you sign in with. Reporting an error, or asking for this article to come down? Use the Report form below.
Report an error or request a takedown
Reports go to the site's administrators. Nothing is removed automatically.