Yukino27 downloadsInstall and update plugins from private GitHub repositories using device-local credentials.
Install and update Obsidian plugins from public or private GitHub Releases, using credentials linked through Obsidian SecretStorage.
VaultFetch is prepared for the Obsidian Community directory but is not listed yet. A public GitHub repository or release does not imply directory approval.
While submission is pending:
main.js, manifest.json and styles.css from the latest release.vault-fetch under the vault's configuration folder, in plugins/.After approval, install it from Settings → Community plugins → Browse. VaultFetch itself is updated using Obsidian's native update mechanism; it cannot install or update itself.
Requires Obsidian 1.11.4+ for SecretStorage. The implementation avoids Node.js and Electron and uses the vault's configured directory. Desktop and mobile compatibility still depends on Obsidian exposing the required plugin lifecycle methods; VaultFetch checks them before writing plugin code.
owner/repository or its HTTPS GitHub URL, then preview the release.Leave the release tag empty to follow the latest stable release. Enter a tag to pin a version. Tags must match the manifest version, optionally with a v prefix.
Updates preserve the target plugin's data.json and other non-code files. Automatic updates never silently reinstall a missing plugin or switch a managed plugin to a different ID. Stop managing removes only VaultFetch's source record; it does not uninstall the plugin.
Each target release must provide:
manifest.json: valid plugin ID, name, version, minimum Obsidian version, description and author.main.js: the compiled plugin entry point.styles.css: optional.Additional repository files and runtime modules are not installed. Bundle dependencies into main.js or use another distribution method if the target needs extra files. Draft releases are rejected; a prerelease may be selected by its explicit tag.
Asset limits: manifest 64 KiB, JavaScript 20 MiB, CSS 2 MiB. Download sizes and available GitHub SHA-256 digests are checked before installation. A digest validates the downloaded asset against GitHub metadata; it does not establish trust in its publisher.
api.github.com for release metadata and assets. Obsidian's networking stack handles GitHub's download redirects. Repository links open only when clicked.data.json stores secret names, source identities and preferences, not token values. VaultFetch does not synchronize secrets or claim they are portable between devices.transactions/. Only manifest.json, main.js and styles.css are backed up and replaced. Unrecoverable or externally changed transactions are retained rather than overwritten.npm ci --ignore-scripts
npm run check
npm run build
Node.js 22+ is used only for development. Runtime dependencies are bundled into the release entry point; license notices are embedded in the build.
A release tag must exactly match manifest.json, for example 0.1.0 (not v0.1.0). The release workflow builds from the tagged source and uploads main.js, manifest.json and styles.css separately.
Directory submission is through Obsidian Community, following the official submission guide. It requires the publisher's Obsidian/GitHub account connection and directory review. No submission is implied by this repository.
MIT. Bundled dependency notices are included in main.js.