Portal Community

What Certified Signals

A Certified badge tells users that an admin reviewer has personally validated the package against a specific criteria scorecard — not just an automated scan. Users evaluating Certified packages can trust that:

Complete Certified Criteria

CriterionRequirementEvidence Required
DocumentationREADME with: install guide, configuration reference, example usage, known limitationsURL to documentation site or README — publicly accessible
Test Coverage80%+ test coverage on node library components. For Form/Workflow/App packages: integration test report covering key scenarios.Test report file (PDF or HTML) uploaded during application
Security ScanClean scan result at time of application — no Critical or High findingsAutomatic rescan on application submission
Open Critical IssuesZero open critical issues at time of applicationChecked automatically against issue tracker
ChangelogComplete changelog from v1.0.0 to current version with meaningful entries per versionReviewed by admin in the version history section
Package is PublishedPackage must be in Published (live) status — cannot certify a DraftStatus verified automatically

Benefits of Certified Status

BenefitDescription
Search ranking boost6% bonus to the certification component of the search ranking formula
Featured slot eligibilityRequired trust level for homepage featured placement (alongside Gold+ tier)
Reputation points+100 reputation points credited to the publisher immediately on certification grant
Certified Publisher badgePublisher earns the "Certified Publisher" profile badge if this is their first certified package
Blue ribbon badgeCertified badge displayed on all package cards and the detail page header

Review Timeline

Certified applications are reviewed within 3–5 business days of submission. The package remains live with Community certification during the review period — there is no status change visible to the public while the application is pending.