Skip to content
This repository was archived by the owner on Sep 23, 2025. It is now read-only.

Security: Coko-Foundation/pubsweet

Security

Security.md

Security Policies and Procedures

This document outlines security procedures and general policies for PubSweet.

Reporting a Bug

We take all security bugs in PubSweet seriously and we thank you for improving its security. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.

Report security bugs by emailing the lead developer, Jure Triglav, at jure (at) coko.foundation.

The lead developer will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating the next steps in handling your report. After the initial reply to your report, the security team will try to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.

You can also report a vulnerability through npm, with the option of submitting a vulnerability directly for a specific package, e.g. pubsweet.

Disclosure Policy

When the security team receives a security bug report, they will coordinate the fix and release process, involving the following steps:

  • Confirm the problem and determine the affected versions.
  • Audit code to find any potential similar problems.
  • Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible to npm.

Comments on this Policy

If you have suggestions on how this process could be improved please submit a merge request.

There aren’t any published security advisories