Skip to content

Docs/security policy#78

Merged
itsdakshjain merged 3 commits into
Py-Contributors:mainfrom
Pranav-MSK:docs/security-policy
Jun 1, 2026
Merged

Docs/security policy#78
itsdakshjain merged 3 commits into
Py-Contributors:mainfrom
Pranav-MSK:docs/security-policy

Conversation

@Pranav-MSK

Copy link
Copy Markdown
Contributor

Description

Adds SECURITY.md with a private vulnerability reporting workflow. Closes #52


Type of Change

  • feat
  • fix
  • docs
  • refactor
  • chore
  • accidental genius

Checklist

Overengineering Verification

  • I have introduced at least one unnecessary abstraction layer
  • The solution is more complex than the problem warrants
  • A reasonable engineer would question at least one design decision
  • I have named something in a way that requires further explanation

Validation

  • pytest passes locally with no failures
  • New functionality is covered by tests
  • I have not deleted tests to make CI green
  • Documentation has been updated if needed

Traceability

  • This PR references a related issue
  • The branch name vaguely reflects the chaos introduced

General

  • Future contributors may question my decisions, but not my confidence
  • Code has been self-reviewed
  • No secrets, credentials, or hardcoded paths were smuggled in
  • I have read the CONTRIBUTING.md guidelines

Screenshots (if applicable)


Additional Notes


"Any fool can write code that a computer can understand. Good programmers write code that humans can understand — but we don't do that here."

Added a security policy document outlining supported versions, vulnerability reporting procedures, and scope.

Signed-off-by: Pranav M S Krishnan <pranavmskrishnan@gmail.com>

@itsdakshjain itsdakshjain left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this pr consist of a commit from another merged pr
can you verify it

@github-actions

Copy link
Copy Markdown

✅ Logic Verified!

The Automated Logic Suite has confirmed that 1 is still 1.

  • Environment: Ubuntu-latest
  • Status: Mathematical Sanity Confirmed

You are safe to merge this chaos.

@Pranav-MSK

Copy link
Copy Markdown
Contributor Author

i pulled the code of conduct from the main branch before the pr. Its fine. Both are the same files, there won't be any conflict

Signed-off-by: Daksh Jain <dakshjain1265@gmail.com>
@github-actions

Copy link
Copy Markdown

✅ Logic Verified!

The Automated Logic Suite has confirmed that 1 is still 1.

  • Environment: Ubuntu-latest
  • Status: Mathematical Sanity Confirmed

You are safe to merge this chaos.

@itsdakshjain itsdakshjain left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made some changes and shorten it for ease and solved branch conflict
Look into it once if you think need to change anything otherwise
Will be merged Tommorow

@Pranav-MSK

Copy link
Copy Markdown
Contributor Author

seems fine to me.

@itsdakshjain itsdakshjain left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merging

@itsdakshjain itsdakshjain merged commit 42527de into Py-Contributors:main Jun 1, 2026
1 check passed
@itsdakshjain

Copy link
Copy Markdown
Member

hey if you like contributing to is-one-one, star the repo and follow it
https://github.com/itsdakshjain

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: Implement a standard Security Policy

2 participants