Open-source project
SilentVoid13/Templater avatar
SilentVoid13/Templater

Templater's README warns that it runs arbitrary JavaScript and system commands in your notes

A template plugin for obsidian

5,400 stars341 forksTypeScriptAGPL-3.0

At a glance

What is it?
An Obsidian plugin with a templating language and a JavaScript escape hatch: the file's own warning section comes before the resources, the manifest pins the licence to AGPL-3.0-only, the maintainer and the original creator are funded separately, the test suite drives a real application, and the bundler's version floor dates from 2021.
Who is it for?
Templater fits someone who wants their notes generated by code rather than typed, and it is a poor fit for a vault where notes come from anywhere you do not control, because the plugin's own README says so in two sentences. Four things to know.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 6 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • SilentVoid13/Templater5,400 ★ · +99
Star history
Repository2026-09-232026-11-15
SilentVoid13/Templater5.3k5.4k

99 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The warning comes before the features, and it says what the plugin does

This README is unusual in where it puts its warning.

The order is: what the plugin is, a link to the documentation, then a section headed Warning, then the community links, then the resources. The warning comes right after the documentation link, above every gallery link and every tutorial.

It says the plugin allows you to execute arbitrary JavaScript code and system commands. Then it says it can be dangerous to execute arbitrary code or system commands from untrusted sources, and to run only code and commands that you understand, from trusted sources.

That is the whole security model of the project in three sentences. A template is not a document with placeholders; it is a program that runs inside your notes application with your privileges, and a template you downloaded from a forum is a program you have not read.

The description of what the plugin does is one sentence long and appears above the warning: it defines a templating language that inserts variables and function results into your notes, and it lets you execute JavaScript manipulating those variables and functions. The order is deliberate, because the feature and the hazard are the same feature.

The repository's one-line description is much terser than that, five words naming a category and a host application, and the package manifest's is a third phrasing again. Of the three descriptions, only the README's mentions that the thing executes code.

Two maintainers, two sets of funding links, and one of them is preferred

The support section is two paragraphs, and they are not symmetric.

The first asks you to support the current maintainer, names them with a profile link, and offers a sponsorship platform as the preferred method plus a coffee-funding page as the other. Two links.

The second asks you to support the original creator, names them with a profile link, and offers a sponsorship platform as the preferred method plus a direct payment button. Two more links, one of which is a hosted payment form with an identifier in its query string.

The repository is named for the original creator and lives under their account, and the current maintainer otherwise appears in the file only as the author of one templates showcase in the resources list.

That handover is documented rather than implied, which is rarer than it should be.

The engine is pinned to one exact application version and the bundler to 2021

Three pins in the development dependencies describe how this plugin is built, and they disagree about what era the project is in.

The application SDK is pinned to an exact version with no range at all. So the plugin compiles against one specific release of the host application, and the moment the host moves, the build needs a change before anything else can happen. For a plugin that runs inside someone else's application, that is a reasonable constraint, and pinning it exactly is the correct way to write it.

The bundler is pinned with a range whose lower bound is a release from 2021. That puts it well behind the 9.x linter in the same list.

The third is the type definitions for the Node runtime, whose lower bound is a 14.x release. So a project with a current linter and a pinned host SDK is typed against an old Node runtime.

None of this is a security problem. It does mean the build toolchain is a mix of eras, and it is one of the reasons a plugin that executes arbitrary code should be built with a bundler you would recognise from another project rather than one that has been frozen for four years.

The test suite drives a real application, and the build runs before it

The test command is not a unit test runner. It is a browser automation framework, configured by a separate file at the repository root, with its own lint rules.

The script chain is: a pretest step that runs the production build, then the automation runner. So the suite tests a built bundle, and a failure in the build stops the tests before they start.

The framework is a distributed one. There is a command line tool, a globals package, a local runner, a test framework adapter, and a reporter, all at the same version, plus assertion libraries and a promise-aware extension to them. And there is a lint plugin for the framework's own globals, so a test that uses an undeclared global is a lint error rather than a runtime surprise.

This is the slow way to test and it is the right way for this kind of project. A plugin's whole surface is the interaction between a template engine, a host application, the file system and the settings panel, and none of that is reachable by calling an exported function. The cost is that a red test gives you a browser trace rather than a stack trace, and that the suite is slow enough to be run less often than a unit suite would be.

The documentation is built by a different toolchain again, served by a command that points at the documentation directory.

The release is cut by a tool with the version prefix set to nothing

Versioning here is entirely automated, and the configuration is at the root of the repository as well as in the manifest.

The release script runs a conventional-versioning tool with the tag prefix argument set to an empty string. So the tags this project cuts have no leading letter in them, and the version in the manifest is the number the tool writes.

The three most recent releases show the shape. A minor release, 2.26.0, and about three weeks before it a patch release and a beta for the next patch. The patch and the beta are eight minutes apart on the same morning: the patch, then the beta. That is the signature of a release cut, immediately followed by the next one being started, which is what an automated versioning tool does when a change lands during a release.

Two different changelog tools appear in the same manifest. The commit message convention is enforced by one tool, invoked through a script named commit, and the version bump and changelog are produced by the other.

There is also a file in the repository whose entire job is compatibility, mapping plugin versions to the minimum application version each one needs. It is the conventional mechanism for this ecosystem and it means the maintainer maintains a second version line alongside the package version.

Three descriptions of the same plugin, and a licence that differs between two files

The project describes itself three times and the three descriptions are not equivalent.

The repository's one-line description is the shortest: a template plugin, for a named application. The package manifest's description is a different sentence in the imperative, about creating and using templates. And the README's own opening sentence is the only one that mentions what the plugin does, which is define a templating language that inserts variables and function results into notes, and execute JavaScript against them.

So the summary a reader sees in a search result or a package listing is the one that says least, and the sentence that says what it does is the one only a reader who opens the file will find.

The licence has a similar split, and this one has a technical consequence. The repository metadata records the licence as AGPL-3.0. The package manifest records the same licence with a suffix that restricts it to that version, with no permission to use later versions. The metadata identifier does not mention later versions either way.

The licence file itself has an unusual extension for a repository whose other documentation files use .md, and the README's licence section links to that file by name rather than pointing at the root. So the authoritative text is a file whose name a reader has to be told about, and only the manifest states explicitly that later versions are not permitted.

Community templates live in a discussion category, and the tutorials are links with timestamps

The community section is two short paragraphs, and it establishes where everything about the plugin actually happens.

It says to go to the repository's discussions tab to ask questions and to find templates, and it names a category within that tab for sharing templates. So there is no template gallery in this repository and no separate site: the collection of user templates is a label on a discussion board.

The sharing convention is worth noting for what it implies about the warning. Templates are shared as gists, which means a template is a file fetched from the internet and then, per the project's own instruction, executed with the reader's privileges. The warning section and the template gallery are one click apart, and the gallery is reached by following a link that begins by asking you to share what you made.

Below that is a resources list of six links. Five are other people's collections and videos, each attributed to a named person rather than presented as documentation, and one of the video links carries a timestamp in its query string, so it is pointing at a specific moment in a long recording rather than at a tutorial someone wrote.

The three alternatives are even thinner: three repository links with no annotation at all. A reader deciding between this plugin and another gets no criteria from this file, only three more places to read.

Editorial conclusion

Templater fits someone who wants their notes generated by code rather than typed, and it is a poor fit for a vault where notes come from anywhere you do not control, because the plugin's own README says so in two sentences. Four things to know. Anything a template can do, JavaScript and system commands are reachable, so a shared template is executable code, and the README's instruction is to run only what you understand from a source you trust. The build pins the application SDK to one exact version and the bundler to a release from 2021, so both move on the maintainer's schedule rather than yours. The tests drive a real application through a browser automation framework rather than calling functions, which is slow and slow to debug but is the only way to know a plugin works inside its host. And the licence is the copyleft variant that requires anyone offering the plugin as a service to publish their changes.

Frequently asked questions

What is Obsidian Templater?

A plugin for the Obsidian note-taking application that defines a templating language for inserting variables and function results into notes, and that also lets you run JavaScript manipulating those values. The repository is licensed under the copyleft AGPL terms and its documentation is published on a separate site.

How do I install Templater in Obsidian?

The README does not say. It describes the plugin, links the hosted documentation as the place to start, and points at the contributing guide for anyone changing the code. There is no installation section, no download link and no step list in the README itself.

Is Templater safe with templates from other people?

The README has a Warning section that says the plugin allows execution of arbitrary JavaScript code and system commands, that this is dangerous when run from untrusted sources, and that you should run only code and commands you understand, from trusted sources.

Who maintains Templater?

The support section names a current maintainer separately from the original creator, with a sponsorship page and a coffee page for the first and a sponsorship page and a direct payment button for the second, and marks GitHub sponsorship as the preferred method for each.

What are the alternatives to Templater?

The README lists three, as bare repository links with no description: chhoumann/quickadd, garyng/obsidian-temple and avirut/obsidian-metatemplates. It also gathers several community template collections, which are resources rather than alternatives.

Official sources

  1. License: AGPL-3.0
  2. Project website
  3. README
  4. Releases
  5. SilentVoid13/Templater on GitHub

Was this useful?