GET
POST
GET
PATCH
DELETE
GET
POST
GET
DELETE
PUT
DELETE
GET
GET
GET
PUT
DELETE
GET
POST
DELETE
GET
PATCH
DELETE
GET
POST
DELETE
GET
PATCH
DELETE
GET
POST
PUT
DELETE
GET
DELETE
GET
POST
PUT
DELETE
GET
POST
PUT
DELETE
GET
POST
PUT
DELETE
POST
GET
GET
PUT
DELETE
GET
GET
GET
PATCH
DELETE
GET
GET
GET
POST
GET
GET
GET
GET
GET
GET
GET
PUT
DELETE
GET
GET
POST
GET
DELETE
GET
POST
GET
POST
GET
GET
PUT
DELETE
GET
POST
GET
POST
GET
PATCH
DELETE
GET
PATCH
GET
GET
POST
POST
POST
GET
PATCH
DELETE
GET
POST
GET
DELETE
GET
PUT
DELETE
POST
POST
GET
POST
PUT
DELETE
GET
POST
GET
GET
GET
GET
GET
GET
POST
GET
PATCH
DELETE
POST
GET
GET
GET
PATCH
DELETE
GET
POST
GET
GET
GET
GET
GET
POST
GET
GET
GET
GET
PUT
GET
GET
GET
GET
POST
GET
PUT
DELETE
GET
POST
GET
GET
POST
GET
PATCH
DELETE
GET
This endpoint will return all community profile metrics, including an overall health score, repository description, the presence of documentation, detected code of conduct, detected license, and the presence of ISSUE_TEMPLATE, PULL_REQUEST_TEMPLATE, README, and CONTRIBUTING files.
The health_percentage
score is defined as a percentage of how many of
these four documents are present: README, CONTRIBUTING, LICENSE, and
CODE_OF_CONDUCT. For example, if all four documents are present, then
the health_percentage
is 100
. If only one is present, then the
health_percentage
is 25
.
content_reports_enabled
is only returned for organization-owned repositories.