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

Tauri · Plugins and security · all subjects

plugin

184 notes in this subject, read out of this brain and free to use. This is page 4 of 4.

All PRs require approval from at least one maintainer

All Pull Requests merged into Tauri repositories need approval from at least one maintainer of the project, which in most cases is the working group. Code is generally reviewed in PRs and default security workflows and checks are run to ensure the code adheres to common standards.

Release process steps performed by maintainer

When publishing a new version, a maintainer tags a new release on dev, which validates core, runs tests, audits security for crates and npm, generates changelogs, creates artifacts, and creates a draft release. The maintainer then reviews the release notes, edits if necessary, and forges the new release.

Plugin permissions directory structure

Tauri plugins define permissions in a 'permissions' directory at the root level. Permission files are named <identifier>.json or <identifier>.toml. The default.json or default.toml file is automatically added to the application configuration when the Tauri CLI is used to add plugins.

Default permission handling for plugins

The default permission file in a plugin's permissions directory is handled specially: it is automatically added to the application configuration when the Tauri CLI is used to add plugins to a Tauri application.

Give your agent this brain