Skip to content

Add security policy contact details and a SECURITY-INSIGHTS file #306

Closed

Description

@kilodesodiq-arch

Problem Statement. SECURITY.md directs reporters to "the contact information in
the README." README.md has no security contact.

Technical Context.
SECURITY.md,
README.md,
.github/SECURITY-INSIGHTS.yml.

Expected Outcome.

  • SECURITY.md lists security@chainforge.app (or GitHub Security Advisories
    fallback).
  • A .github/SECURITY-INSIGHTS.yml file declares supported versions, languages, and
    security policy.

Acceptance Criteria.

  • A test command gh api repos/ChainForgee/ChainForge/security-advisories returns the
    configured contact.

Files or modules likely to be affected.
SECURITY.md,
new .github/SECURITY-INSIGHTS.yml,
README.md.

Difficulty. Easy
Estimated effort. XS



Backlog item #98 from `docs/maintainer-issue-backlog.md.

Activity

  1. egwujiohaifesinachiperpetual-max commented on Jul 15, 2026

    @egwujiohaifesinachiperpetual-max
    Contributor

    Hello boss, Please assign this issue to me. i checked it out and im confident i will solve it
    my eta is 4 hours

  2. BigJohn-dev commented on Jul 15, 2026

    @BigJohn-dev
    Contributor

    I would like to fix this

  3. grantfox-oss commented on Jul 15, 2026

    @grantfox-oss

    🦊 GrantFox — @BigJohn-dev has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

    Next steps:

    1. Open a Pull Request referencing this issue (e.g., Closes #306)
    2. Your PR will be reviewed by the ChainForgee maintainers

    Good luck! Track your progress on GrantFox.

  4. Justprotocol commented on Jul 15, 2026

    @Justprotocol
    Contributor

    Hi Maintainer,

    I would love to help secure the repository by cleaning up these security references. As a frontend and full-stack developer with experience handling repository documentation, strict environment workflows, and API integrations, I can ensure this is implemented cleanly and accurately.

    My approach to fixing this:

    Update SECURITY.md: Add the direct contact email security@chainforge.app and establish the fallback path to GitHub Security Advisories.

    Update README.md: Add or clean up the dedicated security contact section so reporters have a clear path of action.

    Create Security Insights: Add the new .github/SECURITY-INSIGHTS.yml file containing the project's supported versions, development languages, and active security policy declaration.

    Validation: Verify the changes locally and run the gh api repos/ChainForge/ChainForge/security-advisories command to ensure the contact configuration resolves correctly.

    Ready to jump on this and get it sorted quickly!

  5. grantfox-oss commented on Jul 23, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

    @BigJohn-dev's PR #312 was approved and merged by @kilodesodiq-arch.

    🏆 @BigJohn-dev: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,647 total points). Track your full progress on GrantFox.

    👏 Great work, @BigJohn-dev! Keep contributing to ChainForgee.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions