Documentation

Content Scoring

This topic describes how content is scored.

Scores displayed when browsing content are the average of the content’s Community Score and Quality Score. Content Scoring is in early iterations, to be improved with user feedback and future additions to ansible-lint.

Community Score

  • The Community Score is calculated from community surveys submitted by Galaxy users
  • Maximum score of 5.0

Quality Score

  • The Quality Score is based on analysis from yamllint ansible-lint and import-time checks
  • Maximum score is 5.0
  • The Quality Score is the average of Syntax Score and Metadata Score

Note

Scoring is only done at import, to re-score please re-import

Linters Used

  • yamllint is run with a custom config
  • ansible-lint is run using its default rules, for information on how to fix Ansible Lint issues, see the descriptions in the default rules
  • import-time checks reference the Galaxy database, checking for valid platforms, valid cloud platforms, and loadable dependencies

Syntax Score

Linter issues applied to the Syntax Score are yamllint and non-metadata ansible-lint

Each linter issue is subtracted from a max score of 5.0:

  • Issue severity of “VERY_HIGH” reduces the score by 1.0
  • Issue severity of “HIGH” reduces the score by 0.5
  • Issue severity of “MEDIUM” reduces the score by 0.25
  • Issue severity of “LOW” reduces the score by 0.125
  • Issue severity of “VERY_LOW” reduces the score by 0.075
  • Issue severity of “INFO” does not reduce the score

Metadata Score

Linter issues applied to the Syntax Score are metadata ansible-lint and import-time checks

Each linter issue is subtracted from a max score of 5.0:

  • Issue severity of “VERY_HIGH” reduces the score by 1.0
  • Issue severity of “HIGH” reduces the score by 0.5
  • Issue severity of “MEDIUM” reduces the score by 0.25
  • Issue severity of “LOW” reduces the score by 0.125
  • Issue severity of “VERY_LOW” reduces the score by 0.075
  • Issue severity of “INFO” does not reduce the score