Contest a listing

How to remove or correct a listing.

OSS Protector publishes a shared review feed. If you're listed and believe it's wrong, here's how to fix it — there are two paths.

OSS Protector is informational, not a verdict.

The feed is shared context for maintainers. Being listed doesn't block you from contributing — it just means at least one signal was captured. Most listings are correctable by the repository's own maintainer.

1. Ask a repo maintainer to correct it (fastest)

If the report came from a specific pull request, the easiest path is to ask a maintainer of that repo (anyone with OWNER, MEMBER, or COLLABORATOR association) to post a correction command in any PR comment:

@oss-protector dismiss # mark all open reports on this PR's author as dismissed
@oss-protector allow # permanently allowlist the PR author

The bot posts a confirmation comment, dismisses the open reports, and records a negative correction signal that lowers the published score within seconds. Non-maintainer comments using those verbs are ignored.

2. Open a delisting request with us

If no maintainer is reachable, or the issue is with the score or reason rather than the report itself, open a GitHub issue against this project. We respond within a few days and update or remove the listing if warranted.

Open delisting issue

What we'll look at

Whether the original report came from a maintainer.
Whether the cited PR or comment actually contains the abuse pattern in the reason code.
Whether the score has been reinforced by independent corroboration or is dominated by a single report.

If we remove the listing, the public score drops to 0 and the entry no longer appears in the feed. We do not remove the underlying audit log of webhook events — that's how we keep the system honest against retro-edits.

Privacy

We only store GitHub-public account data (login, avatar URL, account type) plus the text of maintainer commands and webhook payloads. See /privacy for the full data scope and retention.