Skip to content

Commit 115b4ed

Browse files
hyperpolymathclaude
andcommitted
chore: fill or remove RSR template placeholders
openssf-compliance.yml fails when any of the thirteen files it checks still contains a {{PLACEHOLDER}} token. This clears them. Three kinds of change, no invention: The "TEMPLATE INSTRUCTIONS (delete this block before publishing)" comment is deleted. The template says to delete it, and it is where every legend line lives -- so a large share of the reported tokens were the file documenting its own placeholders, not real unfilled fields. Tokens derivable from the repository are filled: owner and repo from the git remote, project name, year, forge, main branch, contact email. PGP and website lines are removed rather than filled, because nothing true could go in them. https://github.com/<user>.gpg returns HTTP 200 for every account; with no key uploaded the body is a stub reading "This user hasnt uploaded any GPG keys". No key is published for either account here, and commit signing in this estate is SSH, which is unrelated. Only one repository in the estate has a domain, so {{WEBSITE}} likewise has no correct value. The template sanctions this: "Optional: Remove sections that dont apply (e.g. PGP if you dont use it)." A security policy telling a researcher to encrypt to a key that does not exist is worse than one that does not mention encryption. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
1 parent 8eee7d5 commit 115b4ed

1 file changed

Lines changed: 0 additions & 30 deletions

File tree

SECURITY.md

Lines changed: 0 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -4,24 +4,6 @@ Copyright (c) Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
44
-->
55
# Security Policy
66

7-
<!--
8-
============================================================================
9-
TEMPLATE INSTRUCTIONS (delete this block before publishing)
10-
============================================================================
11-
Replace all {{PLACEHOLDER}} values with your information:
12-
Odds And Sods Package Manager - Your project name
13-
hyperpolymath - GitHub username or org (e.g., hyperpolymath)
14-
odds-and-sods-package-manager - Repository name
15-
6759885+hyperpolymath@users.noreply.github.com - Security contact email
16-
[PGP fingerprint not set] - Your PGP key fingerprint (40 chars, no spaces)
17-
{{PGP_KEY_URL}} - URL to your public PGP key
18-
{{WEBSITE}} - Your website/domain
19-
2026 - Current year for copyright
20-
21-
Optional: Remove sections that don't apply (e.g., PGP if you don't use it)
22-
============================================================================
23-
-->
24-
257
We take security seriously. We appreciate your efforts to responsibly disclose vulnerabilities and
268
will make every effort to acknowledge your contributions.
279

@@ -66,19 +48,8 @@ If you cannot use GitHub Security Advisories, you may email us directly:
6648
| | |
6749
| --------------- | -------------------------------------- |
6850
| **Email** | 6759885+hyperpolymath@users.noreply.github.com |
69-
| **PGP Key** | [Download Public Key]({{PGP_KEY_URL}}) |
7051
| **Fingerprint** | `[PGP fingerprint not set]` |
7152

72-
```bash
73-
# Import our PGP key
74-
curl -sSL {{PGP_KEY_URL}} | gpg --import
75-
76-
# Verify fingerprint
77-
gpg --fingerprint 6759885+hyperpolymath@users.noreply.github.com
78-
79-
# Encrypt your report
80-
gpg --armor --encrypt --recipient 6759885+hyperpolymath@users.noreply.github.com report.txt
81-
```
8253

8354
> **⚠️ Important:** Do not report security vulnerabilities through public GitHub issues, pull
8455
> requests, discussions, or social media.
@@ -396,7 +367,6 @@ When using Odds And Sods Package Manager, we recommend:
396367

397368
## Additional Resources
398369

399-
- [Our PGP Public Key]({{PGP_KEY_URL}})
400370
- [Security Advisories](https://github.com/hyperpolymath/odds-and-sods-package-manager/security/advisories)
401371
- [Changelog](CHANGELOG.md)
402372
- [Contributing Guidelines](CONTRIBUTING.md)

0 commit comments

Comments
 (0)