Skip to content

Security: Let-s-Code-India/.github

Security

SECURITY.md

Security Policy

Thank you for helping keep Let's Code India and the people who use our projects safe.

This policy applies to every repository in the Let-s-Code-India organization that does not have its own SECURITY.md, and to the organization website at https://let-s-code-india.github.io/.

Reporting a vulnerability

Please report suspected vulnerabilities privately. Do not open a public issue, discussion, or pull request with exploit details until a fix is available.

Use either option:

  1. GitHub private reporting: open the Security tab of the affected repository and choose Report a vulnerability (where it is enabled).

  2. Email: write to any of these addresses:

    Please put Security: <repository name> in the subject line. English and Hindi are both fine.

The same contacts are listed in the website's security.txt.

What to include

  • The affected repository, page, or URL, and the version or commit if you know it
  • What you found and what an attacker could do with it
  • Clear steps to reproduce the problem
  • A proof of concept or screenshots, only if they are needed to understand the issue

Please do not include real user data, passwords, or access tokens. If you find a secret or token that was committed by mistake, report it privately and do not use it.

What to expect

We will review your report, acknowledge it, and work on a fix where appropriate. If you would like to be credited, tell us how you want to be named. This is an independent open-source project: we cannot promise a response or fix time, and this policy does not include a bug bounty or any payment.

Supported versions

Security fixes are made on the latest code on the main branch. Unless a repository says otherwise, older commits, tags, and forks are not maintained.

Scope

In scope: code, configuration, and GitHub Actions workflows in this organization's repositories, and the website at https://let-s-code-india.github.io/.

Out of scope: spam, social engineering, denial-of-service testing, reports that only repeat automated scanner output without a demonstrated impact, and problems in third-party services or libraries (please report those to their maintainers).

Good-faith research is welcome. Please avoid accessing, changing, or disrupting data or services that are not yours, and give us reasonable time to fix an issue before sharing details publicly.

More information

There aren't any published security advisories