​
How to report

GitHub private vulnerability reporting

Preferred channel. Opens a private advisory visible only to maintainers, with a coordinated disclosure workflow and CVE issuance built in.
Do not open a public issue for a security report. A public issue on a non-custodial execution system is a disclosure to every reader before a fix exists.
A dedicated security@ address and PGP key are not yet published. Setting up a monitored security mailbox and publishing a key with a real rotation process is a commitment, and an unmonitored address is worse than none — a reporter emails it, hears nothing, and concludes the project does not care.Until that exists, GitHub private advisories are the supported channel. This page will list the address and key fingerprint when they are live.

​
Scope

  • The execution contracts and the scope-signature enforcement path
  • The relayer and executor service
  • The MCP server: auth, keystore, rate limiting, and the read-only guarantee
  • The dashboard API and its authentication gate
  • The Python engine and its HTTP surface
  • Signal and Alpha Ledger hashing and verification
  • Dependency vulnerabilities with a demonstrated path to impact

​
What we care most about

Ranked by what would actually hurt a user:
1

Anything that moves funds outside a signed scope

The one property the whole design exists to guarantee. A bypass of cap, strategy, or expiry enforcement is the highest-severity class.
2

A write reachable from a prompt

The MCP surface is read-only by construction. A path that turns a model-supplied argument into a persisted write is a serious finding even without direct financial impact.
3

Hash or verification forgery

Anything that lets a payload verify against a hash it did not produce breaks the ledger’s entire claim.
4

Key disclosure

Recovery of an API key from the keystore, or a relayer key from the service.

​
What to expect

These are targets for a small team, not a contractual SLA. There is no security on-call rotation. If your report is critical and you have had no response in 72 hours, escalate by opening a non-descriptive public issue asking a maintainer to check their advisories — do not include details.

​
Safe harbour

Good-faith research conducted within this scope, without accessing other users’ data, degrading service, or extracting funds, will not be pursued. Test against your own deployment — Scienter is self-hosted and free to run, so there is no need to test against anyone else’s instance.

​
Credit

Reporters are credited in the advisory and the release notes unless they prefer otherwise. There is no paid bug bounty at this stage, and this page does not imply one.
Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.