checkmk.general
The official Checkmk Ansible Collection - brought to you by the Checkmk company.
Health score
87 / 100
Strong evidence across everything we could observe.
- Excellent (this collection)
- Good
- Fair
- Poor
- Not scored
Observed 6 of 8 signal groups.
Four are needed before a score is published.
4 needed
Category subscores
- Security
- 0%
- Trust
- 100%
- Quality
- 91%
- Maintenance
- 100%
- ansible-core compatibility
- 100%
| Signal | Verdict | What we found | Points | Proved by |
|---|---|---|---|---|
| Signals we could observe | ||||
| security.dependency_boundedness | Not met | 0 of 3 dependencies bounded | 0 / 1 | Published artifact |
| trust.link_claims | Passed | 4 of 4 link URLs declared | 1 / 1 | Published artifact |
| quality.docs | Passed | readme, 44 doc files | 3 / 3 | Published artifact |
| quality.changelog | Passed | changelog.yaml, 5 fragments | 2 / 2 | Published artifact |
| quality.license_quality | Partly met | license file declared, no SPDX id | 0.45 / 1 | Published artifact |
| maintenance.release_recency | Passed | last release 6 days ago | 3 / 3 | Galaxy index |
| maintenance.changelog_recency | Passed | 5 unreleased changelog fragments | 1 / 1 | Published artifact |
| compat.requires_ansible | Passed | >=2.18.0 | 3 / 3 | Published artifact |
| Signals we could not observeNot observed — these are left out of the score rather than counted against it. | ||||
| trust.ansible_membership | Not observed | not shipped in the ansible package | excluded from this score | ansible-build-data |
| quality.tests | Not observed | no test evidence in the published artifact | excluded from this score | Published artifact |
| quality.ci | Not observed | no CI evidence in the published artifact | excluded from this score | Published artifact |
| compat.membership_currency | Not observed | not shipped in the ansible package | excluded from this score | ansible-build-data |
No repository evidence yet. ansible.care has not read any collection's Git repository, so every signal above was proved from a published artifact or from Ansible’s own build data. Tests and CI in particular can be proved present this way but never proved absent — so when we cannot see them, we leave them out of the score rather than counting them against you.
What is costing points
Each of these is a signal we observed and could not fully credit.
- security.dependency_boundedness
Give every collection dependency you declare in `galaxy.yml` an upper or pinned bound — `<`, `<=`, `==` or `~=` — so that installing your collection cannot silently pull in an arbitrary future release of somebody else’s. If your collection declares no dependencies at all this rule already awards full marks and there is nothing here to change. If we reported a dependency we could not read, the fix is the syntax of its version range rather than the dependency itself.
- quality.license_quality
Declare a machine-readable SPDX identifier in `galaxy.yml`’s `license` field rather than relying on a `LICENSE` file alone: an identifier is what a consuming organisation’s policy tooling reads without a human opening the file. A `LICENSES/` directory following REUSE ranks above a bare root licence file and below the identifier. One exception worth stating: we record the identifier you publish rather than validating it against the SPDX list, so a wrong identifier will earn these marks and mislead your users at the same time — if no SPDX identifier fits your licence, publish the file instead.
Links
Authors
- Marcel Arentz (https://github.com/godspeed-you)
- Robin Gierse (https://github.com/robin-checkmk)
- Lars Getwan (https://github.com/lgetwan)
- Max Sickora (https://github.com/Max-checkmk)