vlang/vsl

chore: add SECURITY.md with vulnerability reporting policy

Open

#326 opened on Jul 14, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)V (49 forks)auto 404
Hacktoberfestdocumentationgood first issue

Repository metrics

Stars
 (400 stars)
PR merge metrics
 (PR metrics pending)

Description

No security policy exists in the repo despite wrapping native C libraries (OpenBLAS, LAPACKE, CUDA, Vulkan, HDF5, MPI).

Task

Create SECURITY.md with:

  1. Supported versions (latest release)
  2. Reporting process (email or GitHub Security Advisory)
  3. Response timeline expectation

File

  • New SECURITY.md

Contributor guide

Research direction
Create a new SECURITY.md file following the guidelines provided in the issue. Use the project's existing documentation style and ensure it includes supported versions, reporting process, and response timeline.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90