Skip to main content
Community submissions must be safe, attributable, and honest about behavior.

​
Security requirements

  • Never include secret values (keys, tokens, private credentials).
  • List required secrets by name only.
  • Declare financial and filesystem side effects explicitly.
  • Use least-privilege permission descriptions.
  • Submit only content you have the right to publish.
  • Include attribution for third-party code or copied snippets.
  • Provide clear license context for linked assets.

​
Abuse and quality guardrails

  • No spam or deceptive claims.
  • No malicious instructions or payload references.
  • No harassment in discussions/reviews.

​
Enforcement

  • Submissions may be flagged for changes, rejected, or restricted.
  • Repeated violations can result in temporary or permanent publishing restrictions.

​
Report issues

If you see unsafe or abusive content, open an abuse report in askgina/awesome-gina using the report-abuse.yml issue template and include the PR/submission link.