Repository navigation
docs: add AREX-Skill to community plugins - #388
Conversation
|
Contribution check passed. @hanhainebula, the required catalog checks passed. The centralized source scan returned: failure. Source scanning is advisory for this catalog, so this does not block the PR. Recommended: add scanner CI for securityThis listing can merge without it. HOL still scans We recommend including Adding it:
See SCANNER_GUIDE.md for the recommended workflow. |
kantorcodes
left a comment
There was a problem hiding this comment.
The centralized scan is 53/100, below the 80 merge threshold, with 405 high findings and one low finding. Please remediate or document the rule-level findings; if AREX-Skill lacks source scanner CI, add the SHA-pinned HOL Plugin Scanner workflow from the current SCANNER_GUIDE.md, reproduce with the same pinned scanner, link the source run, rerun the centralized catalog scan, and request re-review once the score is at least 80 and required checks are green.
Centralized scanning and source-repository scanner CI are advisory under the current repository policy, so this review no longer represents merge requirements.
|
@hanhainebula, this contribution is merged into HOL's catalog. Claim your pluginStill syncingThese repositories are merged into HOL's catalog but are not live in the HOL Registry yet:
No action is needed yet. Once the listing appears in the Registry, ownership verification will be available from the plugin dashboard. |
|
Hi @hanhainebula — a quick follow-up about your plugin The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard. Verify ownership with the GitHub account that owns the repository to unlock the owner-verified badge, plugin analytics, and the author dashboard. No repository write access is needed. We may follow up again later if ownership verification is still incomplete. If you already completed verification, no action is needed — the next scheduler run will stop these reminders. |
No description provided.