Skip to content

Conversation

@ThatGuyLLC
Copy link

@ThatGuyLLC ThatGuyLLC commented Oct 22, 2025

The Security Council has approved a new SECURITY.md aligned with the bug-bounty process. Please update your project’s SECURITY.md with the correct links for your project and confirm that private vulnerability reporting is enabled for your repository. All bug bounty details found here:
https://opensourcecommittee.docs.intersectmbo.org/about/paid-open-source-model-posm/bug-bounty-program'

Description

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • Any semantic changes to the specifications are documented in CHANGELOG.md
  • Code is formatted according to CONTRIBUTING.md
  • Self-reviewed the diff

carlostome
carlostome previously approved these changes Oct 22, 2025
Copy link
Collaborator

@carlostome carlostome left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Collaborator

@WhatisRT WhatisRT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a template with some things left for us to fill in.

I wonder if it even makes sense to have this template for this repository. We're not producing code that is used in production, our code only runs for testing purposes. What do other repositories that provide testing infrastructure do here?

@carlostome carlostome dismissed their stale review October 22, 2025 12:25

Missing bits

@ThatGuyLLC
Copy link
Author

feel free to utilize it as you wish, it just serves that if something was found in the code that could effect running in another project this is a way to report it and a bounty is possible

ThatGuyLLC and others added 3 commits November 18, 2025 16:30
The Security Council has approved a new SECURITY.md aligned with the bug-bounty process. Please update your project’s SECURITY.md with the correct links for your project and confirm that private vulnerability reporting is enabled for your repository.
All bug bounty details found here:
https://opensourcecommittee.docs.intersectmbo.org/about/paid-open-source-model-posm/bug-bounty-program'
vulnerability, please mention them in your email but ***DO NOT*** attempt to include them as
attachments as this may cause your Email to be blocked by spam filters.
See the security file in the [Cardano engineering handbook](https://github.com/input-output-hk/cardano-engineering-handbook/blob/main/SECURITY.md).
If you discover a security vulnerability in formal-ledger-specifications, we encourage you to responsibly disclose it to us. To report a vulnerability, please use the [private reporting form on GitHub](https://github.com/IntersectMBO/formal-ledger-specifications/security/advisories/new) to draft a new _Security advisory_.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The link in this line is a 404.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like secure submission of security advisories is not enabled on this repo. @ThatGuyLLC could you please enable it.

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.

6 participants