new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Electron · Tutorial · all subjects

security checklist & fuses

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Electron security reporting via GitHub Security Advisory

Report security issues in Electron using the GitHub Security Advisory 'Report a Vulnerability' tab at https://github.com/electron/electron/security/advisories/new. The Electron security team will send an initial response indicating next steps and keep you informed of progress toward a fix and full announcement.

Escalation procedure for Electron security reports

If you do not receive acknowledgement of a security report within 6 business days, or cannot find a private security contact, escalate to the OpenJS Foundation CNA at security@lists.openjsf.org. Escalation is also appropriate if the project acknowledges the report but provides no further response or engagement within 14 days.

Report third-party module security issues to maintainers

Security bugs in third-party modules should be reported directly to the person or team maintaining the module. Vulnerabilities can also be reported through the npm contact form by selecting 'I'm reporting a security vulnerability'.

Give your agent this brain