dux_fortinet.fortisase_beta

What is costing points

Each of these is a signal we observed and could not fully credit.

• quality.docs

  Ship your README and your `docs/` directory INSIDE the published tarball, not only in your Git repository — we do not read repositories at all yet, so a file that exists only there is a file we cannot see. If your `build_ignore` excludes `docs/`, that exclusion is why we observed nothing. Beyond the README this rule counts documentation FILES, so splitting a long README into per-module and per-role pages is what moves it; adding filler pages to raise a count would satisfy the arithmetic and help nobody.

• 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.

• maintenance.release_recency

  Cut a release to Galaxy. This is the heaviest single rule in the rubric because a release is the one unambiguous, publisher-controlled act of maintenance we can observe without reading your repository — which is also its limitation, and worth saying plainly: a collection under active development that rarely releases is under-credited here, and that is a gap in what we can see rather than a judgement about the work. If your collection is finished rather than abandoned, there is nothing here you should change on our account.

• maintenance.changelog_recency

  Write a fragment into `changelogs/fragments/` as each change lands, rather than composing release notes at release time. This reads the same published file as the Quality changelog rule, so shipping and maintaining a changelog answers both at once — if a page told you twice to ship a changelog it would be describing one missing file as two problems. One thing this rule does NOT ask for: an empty fragments directory is not the goal, and cutting a release clears your fragments by design. A maintained changelog with nothing pending still earns partial credit here, so releasing your work does not cost you this rule.