Skip to content

docs: add SECURITY.md with security policy and best practices - #641

Merged
kjur merged 1 commit into
kjur:masterfrom
njg7194:add-security-policy
Feb 20, 2026
Merged

kjur merged 1 commit into
kjur:masterfrom
njg7194:add-security-policy

Conversation

@njg7194

@njg7194 njg7194 commented Feb 1, 2026

Copy link
Copy Markdown

Summary

This PR adds a SECURITY.md file to establish security reporting guidelines and best practices for users.

Changes

  • Added comprehensive SECURITY.md with:
    • Vulnerability reporting process
    • Response timeline expectations
    • Security best practices for key management
    • Algorithm selection recommendations
    • Input validation guidelines
    • Known security considerations

Motivation

As a widely-used cryptography library (3M+ weekly npm downloads), jsrsasign benefits from:

  1. Clear vulnerability reporting channels
  2. Documented security best practices for users
  3. Guidance on secure implementation patterns

This follows GitHub's security best practices and helps protect the community of users who depend on this library.

@kjur
kjur merged commit e2e417e into kjur:master Feb 20, 2026
1 check passed
@kjur

kjur commented Feb 20, 2026

Copy link
Copy Markdown
Owner

Hi @njg7194 , thank you kindly for your PR. I've merged it. Thank you.

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.

2 participants