My Certifications
The certifications section of the publisher workspace shows earned certifications, in-progress applications, and the criteria available to pursue — giving publishers a clear roadmap to increase their package trust level.
Certification Status Sections
| Section | What It Shows |
|---|---|
| Earned Certifications | Packages that have achieved Certified status — with the date granted |
| In Progress | Certification applications submitted but not yet reviewed — with estimated review completion |
| Available to Apply | Published packages that meet the minimum criteria and are eligible for Certified application |
| Not Eligible | Published packages that do not yet meet criteria — with a checklist showing what's missing |
Certification Criteria Checklist
For each package in "Available to Apply" or "Not Eligible", the workspace shows a checklist of the Certified criteria:
| Criterion | Status Display |
|---|---|
| README / documentation URL | Provided or Missing |
| Test coverage report (80%+) | Coverage percentage with Passes or Below 80% |
| Security scan — no Critical/High findings | Last scan date with Clean or Findings |
| Open critical issues | Count of open critical issues — must be 0 |
| Changelog completeness | Complete or Incomplete |
Applying for Certified Status
Verify All Criteria Are Met
Confirm all checklist items show green before applying. Submitting with failing criteria will result in rejection and waste the review cycle.
Submit Evidence
Upload the test coverage report (PDF or HTML) and provide the documentation URL. These are reviewed by the admin.
Await Review
Estimated 3–5 business days. The package remains published in Community tier while the application is under review.
Receive Decision
Approved: Certified badge applied immediately, 100 reputation points credited. Rejected: feedback provided explaining which criteria were not met. Publisher can address and reapply.