You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add security policy contact details and a SECURITY-INSIGHTS file #306
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.
Activity
egwujiohaifesinachiperpetual-max commentedon Jul 15, 2026
Hello boss, Please assign this issue to me. i checked it out and im confident i will solve it
my eta is 4 hours
BigJohn-dev commentedon Jul 15, 2026
I would like to fix this
grantfox-oss commentedon Jul 15, 2026
🦊 GrantFox — @BigJohn-dev has been assigned to this issue as part of the Official Campaign | FWC26 campaign!
Next steps:
Closes #306)Good luck! Track your progress on GrantFox.
Justprotocol commentedon Jul 15, 2026
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!
grantfox-oss commentedon Jul 23, 2026
🎉 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.