Only the latest release of @binalyze/notar is supported with security updates.

• v2.0.0 — Fixed two verification-verdict issues where valid: true did not guarantee the file was signed by the expected identity. verifyFromAuthor now binds the verdict to a trusted publisher: a present-but-failing signature is fatal, an optional expectedPublisher scopes the verdict to a chosen identity, and the unauthenticated author field is surfaced as claimed. The web app no longer silently falls back from a user-pinned public key to publisher-resolved verification. Upgrading to 2.0.0 is required to pick up these fixes; the verdict-semantics change is the reason for the major version bump.

• v2.0.1 — Key discovery no longer trusts the publisher string from the file being verified. Previously it was concatenated into the key-manifest URL and a startsWith("localhost") check selected plain HTTP, so a value such as localhost@attacker.test:5125 fetched keys over HTTP from an attacker host while the UI reported HTTPS. Publishers are now validated as bare hostnames, manifests are fetched over HTTPS only (no redirects, 5 s timeout, 64 KiB cap, schema-checked), plain HTTP is limited to localhost/127.0.0.1 behind an explicit allowInsecureLocalhost opt-in, keySource reports the real transport, signature count is capped at 16, and file-derived strings are escaped before display. New error codes: INVALID_PUBLISHER, TOO_MANY_SIGNATURES.

Please report security vulnerabilities through GitHub Security Advisories.

Do not open a public issue for security vulnerabilities.

• Acknowledgment: Within 48 hours of your report.
• Resolution: We aim to release a fix within 90 days of a confirmed vulnerability.
• Disclosure: We will coordinate disclosure timing with you.

The following are in scope for security reports:

• Cryptographic weaknesses (signature forgery, key leakage)
• Key handling issues (improper storage, exposure)
• SSRF or injection vulnerabilities in the web worker
• Worker abuse or bypass of verification logic

• Social engineering attacks
• Denial of service against the public instance
• Issues in dependencies (report these upstream)