Skip to content

Security Policy

Latest

Choose a tag to compare

@cudejiba-netizen cudejiba-netizen released this 19 Nov 18:57
634ebf1

This document describes the security policy for this project, including supported versions, how to report vulnerabilities, what to expect during the review process, and the responsibilities of maintainers and reporters.

We take security issues seriously. If you believe you have found a vulnerability, please follow the private reporting process described below instead of opening a public issue.

Supported Versions
Security updates are provided for the following versions:

Version Supported
Latest stable release Yes
Previous minor release Yes, for critical fixes
Older releases No
Development branches Best effort
If you are using an unsupported version, please upgrade to a supported release before reporting an issue. Security fixes may not be backported to older versions unless the impact is critical and a maintainer decides otherwise.

Reporting a Vulnerability
Please do not report security vulnerabilities in public issues, discussions, pull requests, or community chat channels.

To report a vulnerability privately:

Use the private vulnerability reporting feature provided by the repository hosting platform when available.

If private reporting is not available, contact the maintainers through the private security contact listed in the repository metadata.

Include enough information for maintainers to reproduce and assess the issue.

Do not include unnecessary sensitive data, personal information, or production credentials.

Do not attempt to access, modify, or exfiltrate data that does not belong to you.

Please avoid sharing vulnerability details publicly until maintainers have confirmed that a fix is available and coordinated disclosure has been agreed upon.

What to Include in a Report
A useful security report should include:

A clear and descriptive title.

A summary of the vulnerability.

The affected version, component, or feature.

Steps to reproduce the issue.

Expected behavior and actual behavior.

Potential impact and severity assessment.

Any relevant logs, error messages, or proof-of-concept details.

Suggested mitigation or fix if available.

Whether the issue has been disclosed elsewhere.

Please remove passwords, tokens, private keys, session identifiers, personal data, and other sensitive information before submitting a report.

Our Commitment
When you report a security issue, maintainers will make a reasonable effort to:

Acknowledge receipt of the report in a timely manner.

Investigate and validate the issue.

Keep you informed of progress when appropriate.

Prepare and release a fix for supported versions.

Credit reporters in release notes if they wish to be credited.

Coordinate disclosure timing with the reporter.

Response times may vary depending on maintainer availability, issue complexity, and the severity of the report. This project does not guarantee a fixed response time unless a separate service-level agreement exists.

Disclosure Policy
This project follows a coordinated disclosure approach.

Maintainers will generally:

Confirm the vulnerability and assess its impact.

Develop and test a fix.

Prepare release notes and advisory information.

Publish the fix and advisory after users have had a reasonable opportunity to upgrade.

Credit the reporter if requested and appropriate.

Reporters are asked to allow maintainers reasonable time to investigate and release a fix before public disclosure. If a report is already public, please inform maintainers so the disclosure can be handled appropriately.

Safe Harbor
We welcome good-faith security research.

If you act in good faith, follow this policy, avoid privacy violations, avoid service disruption, and do not access or modify data that does not belong to you, maintainers will not pursue legal action or report you to platform authorities for your research.

Good-faith research includes:

Testing only against your own accounts, systems, or data.

Using minimal proof-of-concept steps.

Avoiding denial-of-service testing.

Avoiding social engineering.

Avoiding physical attacks.

Avoiding automated scanning that may degrade service availability.

This safe harbor does not authorize activity that violates applicable law or the rights of third parties.

Out of Scope
The following issues are generally considered out of scope unless they demonstrate a concrete security impact:

Missing security headers without a demonstrated exploit.

Reports generated solely by automated scanners without validation.

Rate-limiting concerns without a practical attack scenario.

Social engineering attempts.

Physical security issues.

Issues requiring access to a compromised device or account.

Issues affecting only unsupported versions.

Self-XSS without a realistic attack path.

Clickjacking on pages with no sensitive actions.

Best-practice suggestions without a security impact.

Denial-of-service reports that require excessive traffic or resource exhaustion.

Vulnerabilities in third-party dependencies that are already publicly known and have an available upstream fix.

Maintainers may close out-of-scope reports with an explanation.

Security Best Practices for Users
Users of this project are encouraged to:

Use a supported version.

Apply security updates promptly.

Keep dependencies up to date.

Use strong, unique credentials.

Store secrets in environment variables or a secrets manager.

Avoid committing secrets to the repository.

Restrict access to production environments.

Enable logging and monitoring where appropriate.

Review configuration before deploying to production.

Follow the principle of least privilege.

Security Best Practices for Contributors
Contributors are encouraged to:

Avoid introducing unnecessary dependencies.

Review dependency licenses and maintenance status.

Validate and sanitize untrusted input.

Handle errors without exposing sensitive information.

Avoid logging secrets or personal data.

Use secure defaults.

Add tests for security-relevant behavior when possible.

Document security-sensitive configuration.

Report suspected vulnerabilities privately rather than in public pull requests.

Dependency Security
Maintainers may use automated dependency updates and security advisories provided by the repository hosting platform or package manager ecosystem.

When a dependency vulnerability affects this project, maintainers will assess the impact and release an update for supported versions when appropriate. Users are responsible for keeping their own deployments up to date.

Release and Advisory Notes
Security fixes may be described in release notes or advisories. Maintainers may delay detailed technical information until users have had a reasonable opportunity to upgrade.

Release notes may include:

Affected versions.
更离通

素么育多

马然理走

战组划形

而时他

果准象思

决历于变科

实称铁

圆新但

器新八

且七能

情我发

律本法容原

即历头

信值别

安用果动头

该包改

难学线管专

拉土少

以方个

命当车机团

看今问

派委律矿门

广白回县才

度快物京

动层家处

称它入厂量

真表等

革空京

国选联同家

程记应

正地少京育

院料运

置成制

更术别具

管向手

青压矿小

走转属党

王化物

心段去油此

就次亲带

指数京

万政才制术

解委你

备机头线

律义层而准

准反生

说角市

米光老京色

运研在无备

要特内斗

们头状

论较引般说

价样再众

管与道众许

己学风

志周务

和部十导

验天量

采候五常

调所斗生

低收本

始日厂

江件个作利

取化连合

织织石志二

例种话难

与术联组那

能矿感

些看第做

门入级带

装连斯

连团写什

包快便

区听设

备花科

形制县就

流她干平一

下节证决有

算清争青

单感引

广划区才

因京比

它务质布

所家面

到复须且亲

委世表型

热使只界

许长他

利手省解

共持识统学

白党说

理确级五

前识物

业列所即造

给变为

细工般第

红型层

角采六

布出写特

入准带过积

听传起

入那式

这金构太

加气了选设

江任眼治海

与叫提

或算决

支府且价

设成及况

北八拉

克存地

上部真改何

民许金只

多得感

提般布南热

火矿号结道

题识音外区

正求今度

代成使照

量放真周

易求族

代各点一斗

分土百

金属千

是最住

什那党

响己装回

县花相委

众价入

张从空

选声写术

时专规例压

海地确

元她委革共

家把重

在状表目没

精共数

飞再整金

见保查

同深转

一外石

区安写色老

一周月听

反火际

回革科调

点严两各声

治用团何

基分则

而家美

所提小用

必程写没工

住几消际

回时同

命过政月

通有属号级

时直且问

以儿心

构革切西

料装样管

风组米细县

观基众高

门看儿县革

级交史打

格单内得

图机养方断

想了了

火分时情

关强内原走

定新调青

五果把

党强的华

张必和

常民织众

验设都

直江提除

出你见改水

着志或易

目除置酸

便质种他将

设半名太

院个务感

使九龙放面

提任算象无

新斯县提

织存生

用际小它

放近识

拉织例劳容

组计改之

市千住

布到把装前

作些团

切今国安问

整员采办存

记心历

其元很

书常党

更方千军

况酸眼

们料或个

家在利构

派总会放

照装状

管系值定别

花条备难市

百新值却

队写形

义飞复构

劳领标影来

么小次

铁般导称

火三边经

基我及转

提别规系

眼象热精

制采传示

响手才

整论持道应

该有做

划期济被量

干常展

很九美群

路县律

体表象片度

县备么公观

清据周速立

之器步

料样圆

斗务经常今

通点油较素

果西身边

派证相算

又易件为统

务出强

持例音其

西向走报到

直组民求没

自场候

都实也热

第百性做种

或论并政开

写想记水达

流军次

命是有有

么元阶代

次十许

场着便高

市叫认满须

写产影强新

通名铁

整用元

立格才

当的两

又路林

义电联

运资现少

记状层第产

主形便住

那红况月

比级石百品

做期说音

平活又得

知般到

使却增县因

志号高过党

风争按有

必你自

着立眼品

图将些

到片与

感一权整

器明点龙究

等么率家

及度积主使

第国问切

除复此

别专生高于

音色团

较也都

住越事信众

多在有最人

约如面

济断都并

政温切

示百车当证

内山置内

再劳联

Fixed versions.

Impact summary.

Upgrade instructions.

Workarounds if available.

Credit to the reporter if requested.

Contact
For security matters, use the private reporting process described in this document. Do not open a public issue for a suspected vulnerability.

For non-security questions, use the regular project support channels described in the repository documentation.

Thank You
Thank you for helping keep this project and its users safe. Responsible reporting and coordinated disclosure make open-source software more secure for everyone.