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
Thanks for opening this issue! We appreciate your contribution. Please make sure you’ve provided all the necessary details and screenshots, and don't forget to follow our Guidelines and Code of Conduct. Happy coding! 🚀
Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible. Stay awesome!
@Dipanita45 asked first, so whatever the maintainer decides on assignment is fine with me - just adding what I'd actually change here, since I went through the same exercise on my own repo recently:
SECURITY.md - right now there is no security policy (GitHub shows "No security policy defined"). Even for a practice repo, a stub pointing people at the Security tab > private reporting keeps random vulnerability reports out of public issues. This is unambiguous in GitHub security section settings.
Dependabot - a small dependabot.yml with package-ecosystem: "npm" + gitsub-module/actions updates. Cheap and enabled from day one.
Secret scanning + push protection - takes 2 clicks in Settings > Advanced Security and blocks anyone from committing a token, and with new contributors every day this matters.
Workflow tokens at least privilege - set permissions: contents: read workflow-level, and specifically the other workflows with comments get more permissions.
Branch protection on main - require PR before merge, so nobody accidentally force-pushes the whole list.
If it's useful, I can submit the SECURITY.md + dependabot.yml PR the moment you assign one of these to me.
Activity
github-actions commentedon Nov 1, 2024
Thanks for opening this issue! We appreciate your contribution. Please make sure you’ve provided all the necessary details and screenshots, and don't forget to follow our Guidelines and Code of Conduct. Happy coding! 🚀
github-actions commentedon Nov 1, 2024
Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible. Stay awesome!
Dipanita45 commentedon Nov 3, 2024
Please assign me this issue
@recodehive
ziadkix commentedon Nov 6, 2026
@Dipanita45 asked first, so whatever the maintainer decides on assignment is fine with me - just adding what I'd actually change here, since I went through the same exercise on my own repo recently:
SECURITY.md- right now there is no security policy (GitHub shows "No security policy defined"). Even for a practice repo, a stub pointing people at the Security tab > private reporting keeps random vulnerability reports out of public issues. This is unambiguous in GitHub security section settings.dependabot.ymlwithpackage-ecosystem: "npm"+gitsub-module/actions updates. Cheap and enabled from day one.permissions: contents: readworkflow-level, and specifically the other workflows with comments get more permissions.main- require PR before merge, so nobody accidentally force-pushes the whole list.If it's useful, I can submit the SECURITY.md + dependabot.yml PR the moment you assign one of these to me.