Security Policy

Verse & Variable

Publication: Verse & Variable
Founder and Editor: Pravinkumar Ghodake
Website: https://pravinkumar-ghodake.github.io/verse-variable/
Repository: https://github.com/pravinkumar-ghodake/verse-variable/


1. Purpose

Verse & Variable takes the security, integrity and availability of its website and associated repository seriously.

This policy establishes a responsible approach to identifying, reporting and addressing potential security vulnerabilities.

The objective is to protect the publication, its contributors, its readers and the integrity of its content.

2. Scope

Security reports may concern:

The policy covers the public website and its associated source repository.

3. Reporting a Vulnerability

Please report suspected security vulnerabilities privately rather than publishing technical details in a public issue.

The preferred contact route is the founder’s official website:

https://sites.google.com/view/pravinkumarghodake

A report should ideally include:

  1. A brief description of the suspected vulnerability.
  2. The affected website page or repository file.
  3. Steps necessary to reproduce the issue, where safe.
  4. Potential impact.
  5. Relevant screenshots or supporting technical information.
  6. Suggested remediation, if known.

Do not include passwords, private access tokens or unrelated personal information in a report.

4. Responsible Disclosure

Please:

Security testing should remain proportionate and responsible.

5. Response and Remediation

Security reports will be reviewed by the publication’s founder.

Where a vulnerability is confirmed, reasonable steps may be taken to:

Response times may vary depending on the nature and complexity of the issue.

6. Supported Versions

The current published version of Verse & Variable is the primary version considered for security review.

Older repository states may not receive independent security maintenance.

7. Third-Party Services

The publication may depend on services and technologies operated by third parties, including:

Security issues within third-party infrastructure should also be reported through the relevant provider’s security reporting process.

8. Security and Privacy Principles

The publication aims to:

9. Recognition

Responsible vulnerability reports are appreciated.

Recognition or public acknowledgement may be considered where appropriate and with the reporter’s consent.

There is no guaranteed financial reward or bug bounty programme associated with this policy.

10. Policy Changes

This security policy may be updated as the website and its technical infrastructure evolve.


Verse & Variable

A line of verse. A line of inquiry.

لفظ سے لہر تک

From the word to the wave.