npmpackage.info

mustache

Minimal templating with {{mustaches}} in JavaScript

4.2.0

16,532

MIT

JavaScript

2.60 kB

855,440,601 2.7

Installations

npm install mustache

Developer Guide

BETA

Typescript

No

Module System

CommonJS, ESM

Node Version

12.19.0

NPM Version

6.14.8 Score

99.8

Supply Chain

100

Quality

79.9

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

36

Total

350

Closed

149

Merged

165

Issues

Open

79

Total

485

Closed

406

Releases

v4.2.0

Published on 28 Mar 2021

v3.1.0

Published on 13 Sept 2019

v3.0.2

Published on 21 Aug 2019

v3.0.1

Published on 11 Nov 2018

v3.0.0

Published on 16 Sept 2018

v2.3.2

Published on 17 Aug 2018

View all 16 releases

Contributors

114

Unable to fetch Contributors

View all 114 contributors

Languages

JavaScript

Mustache

Ruby

HTML

TypeScript

JavaScript (88.04%)

Mustache (7.24%)

Ruby (3.18%)

HTML (1.16%)

TypeScript (0.39%)

Developer

janl

Download Statistics

Total Downloads

855,440,601

Last Day

631,798

Last Week

4,733,739

Last Month

21,431,086

Last Year

236,121,314

GitHub Statistics

16,532 Stars

830 Commits

2,386 Forks

401 Watching

19 Branches

114 Contributors

Bundle Size

6.43 kB

Minified

2.60 kB

Minified + Gzipped

Bundlephobia

Maintainers

Package Meta Information

Latest Version

4.2.0

Package Id

mustache@4.2.0

Size

33.77 kB

NPM Version

6.14.8

Node Version

12.19.0

Publised On

28 Mar 2021

Total Downloads

Cumulative downloads

Total Downloads

855,440,601

Last day

-31.9%

631,798

Compared to previous day

Last week

-9.3%

4,733,739

Compared to previous week

Last month

-3.1%

21,431,086

Compared to previous month

Last year

33.8%

236,121,314

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

chai eslint esm jshint mocha puppeteer rollup uglify-js zuul zuul-ngrok

Versions

mustache.js - Logic-less {{mustache}} templates with JavaScript

What could be more logical awesome than no logic at all?

mustache.js is a zero-dependency implementation of the mustache template system in JavaScript.

Mustache is a logic-less template syntax. It can be used for HTML, config files, source code - anything. It works by expanding tags in a template using values provided in a hash or object.

We call it "logic-less" because there are no if statements, else clauses, or for loops. Instead there are only tags. Some tags are replaced with a value, some nothing, and others a series of values.

For a language-agnostic overview of mustache's template syntax, see the mustache(5) manpage.

Where to use mustache.js?

You can use mustache.js to render mustache templates anywhere you can use JavaScript. This includes web browsers, server-side environments such as Node.js, and CouchDB views.

mustache.js ships with support for the CommonJS module API, the Asynchronous Module Definition API (AMD) and ECMAScript modules.

In addition to being a package to be used programmatically, you can use it as a command line tool.

And this will be your templates after you use Mustache:

'stache

Install

You can get Mustache via npm.

1$ npm install mustache --save

Usage

Below is a quick example how to use mustache.js:

1var view = {
2  title: "Joe",
3  calc: function () {
4    return 2 + 4;
5  }
6};
7
8var output = Mustache.render("{{title}} spends {{calc}}", view);

In this example, the Mustache.render function takes two parameters: 1) the mustache template and 2) a view object that contains the data and code needed to render the template.

Templates

A mustache template is a string that contains any number of mustache tags. Tags are indicated by the double mustaches that surround them. {{person}} is a tag, as is {{#person}}. In both examples we refer to person as the tag's key. There are several types of tags available in mustache.js, described below.

There are several techniques that can be used to load templates and hand them to mustache.js, here are two of them:

Include Templates

If you need a template for a dynamic part in a static website, you can consider including the template in the static HTML file to avoid loading templates separately. Here's a small example:

1// file: render.js
2
3function renderHello() {
4  var template = document.getElementById('template').innerHTML;
5  var rendered = Mustache.render(template, { name: 'Luke' });
6  document.getElementById('target').innerHTML = rendered;
7}

1<html>
2  <body onload="renderHello()">
3    <div id="target">Loading...</div>
4    <script id="template" type="x-tmpl-mustache">
5      Hello {{ name }}!
6    </script>
7
8    <script src="https://unpkg.com/mustache@latest"></script>
9    <script src="render.js"></script>
10  </body>
11</html>

Load External Templates

If your templates reside in individual files, you can load them asynchronously and render them when they arrive. Another example using fetch:

1function renderHello() {
2  fetch('template.mustache')
3    .then((response) => response.text())
4    .then((template) => {
5      var rendered = Mustache.render(template, { name: 'Luke' });
6      document.getElementById('target').innerHTML = rendered;    
7    });
8}

Variables

The most basic tag type is a simple variable. A {{name}} tag renders the value of the name key in the current context. If there is no such key, nothing is rendered.

All variables are HTML-escaped by default. If you want to render unescaped HTML, use the triple mustache: {{{name}}}. You can also use & to unescape a variable.

If you'd like to change HTML-escaping behavior globally (for example, to template non-HTML formats), you can override Mustache's escape function. For example, to disable all escaping: Mustache.escape = function(text) {return text;};.

If you want {{name}} not to be interpreted as a mustache tag, but rather to appear exactly as {{name}} in the output, you must change and then restore the default delimiter. See the Custom Delimiters section for more information.

View:

1{
2  "name": "Chris",
3  "company": "<b>GitHub</b>"
4}

Template:

* {{name}}
* {{age}}
* {{company}}
* {{{company}}}
* {{&company}}
{{=<% %>=}}
* {{company}}
<%={{ }}=%>

Output:

1* Chris
2*
3* &lt;b&gt;GitHub&lt;/b&gt;
4* <b>GitHub</b>
5* <b>GitHub</b>
6* {{company}}

JavaScript's dot notation may be used to access keys that are properties of objects in a view.

View:

1{
2  "name": {
3    "first": "Michael",
4    "last": "Jackson"
5  },
6  "age": "RIP"
7}

Template:

1* {{name.first}} {{name.last}}
2* {{age}}

Output:

1* Michael Jackson
2* RIP

Sections

Sections render blocks of text zero or more times, depending on the value of the key in the current context.

A section begins with a pound and ends with a slash. That is, {{#person}} begins a person section, while {{/person}} ends it. The text between the two tags is referred to as that section's "block".

The behavior of the section is determined by the value of the key.

False Values or Empty Lists

If the person key does not exist, or exists and has a value of null, undefined, false, 0, or NaN, or is an empty string or an empty list, the block will not be rendered.

View:

1{
2  "person": false
3}

Template:

1Shown.
2{{#person}}
3Never shown!
4{{/person}}

Output:

1Shown.

Non-Empty Lists

If the person key exists and is not null, undefined, or false, and is not an empty list the block will be rendered one or more times.

When the value is a list, the block is rendered once for each item in the list. The context of the block is set to the current item in the list for each iteration. In this way we can loop over collections.

View:

1{
2  "stooges": [
3    { "name": "Moe" },
4    { "name": "Larry" },
5    { "name": "Curly" }
6  ]
7}

Template:

1{{#stooges}}
2<b>{{name}}</b>
3{{/stooges}}

Output:

1<b>Moe</b>
2<b>Larry</b>
3<b>Curly</b>

When looping over an array of strings, a . can be used to refer to the current item in the list.

View:

1{
2  "musketeers": ["Athos", "Aramis", "Porthos", "D'Artagnan"]
3}

Template:

1{{#musketeers}}
2* {{.}}
3{{/musketeers}}

Output:

1* Athos
2* Aramis
3* Porthos
4* D'Artagnan

If the value of a section variable is a function, it will be called in the context of the current item in the list on each iteration.

View:

1{
2  "beatles": [
3    { "firstName": "John", "lastName": "Lennon" },
4    { "firstName": "Paul", "lastName": "McCartney" },
5    { "firstName": "George", "lastName": "Harrison" },
6    { "firstName": "Ringo", "lastName": "Starr" }
7  ],
8  "name": function () {
9    return this.firstName + " " + this.lastName;
10  }
11}

Template:

1{{#beatles}}
2* {{name}}
3{{/beatles}}

Output:

1* John Lennon
2* Paul McCartney
3* George Harrison
4* Ringo Starr

Functions

If the value of a section key is a function, it is called with the section's literal block of text, un-rendered, as its first argument. The second argument is a special rendering function that uses the current view as its view argument. It is called in the context of the current view object.

View:

1{
2  "name": "Tater",
3  "bold": function () {
4    return function (text, render) {
5      return "<b>" + render(text) + "</b>";
6    }
7  }
8}

Template:

1{{#bold}}Hi {{name}}.{{/bold}}

Output:

1<b>Hi Tater.</b>

Inverted Sections

An inverted section opens with {{^section}} instead of {{#section}}. The block of an inverted section is rendered only if the value of that section's tag is null, undefined, false, falsy or an empty list.

View:

1{
2  "repos": []
3}

Template:

1{{#repos}}<b>{{name}}</b>{{/repos}}
2{{^repos}}No repos :({{/repos}}

Output:

1No repos :(

Comments

Comments begin with a bang and are ignored. The following template:

1<h1>Today{{! ignore me }}.</h1>

Will render as follows:

1<h1>Today.</h1>

Comments may contain newlines.

Partials

Partials begin with a greater than sign, like {{> box}}.

Partials are rendered at runtime (as opposed to compile time), so recursive partials are possible. Just avoid infinite loops.

They also inherit the calling context. Whereas in ERB you may have this:

1<%= partial :next_more, :start => start, :size => size %>

Mustache requires only this:

1{{> next_more}}

Why? Because the next_more.mustache file will inherit the size and start variables from the calling context. In this way you may want to think of partials as includes, imports, template expansion, nested templates, or subtemplates, even though those aren't literally the case here.

For example, this template and partial:

base.mustache:
<h2>Names</h2>
{{#names}}
  {{> user}}
{{/names}}

user.mustache:
<strong>{{name}}</strong>

Can be thought of as a single, expanded template:

1<h2>Names</h2>
2{{#names}}
3  <strong>{{name}}</strong>
4{{/names}}

In mustache.js an object of partials may be passed as the third argument to Mustache.render. The object should be keyed by the name of the partial, and its value should be the partial text.

1Mustache.render(template, view, {
2  user: userTemplate
3});

Custom Delimiters

Custom delimiters can be used in place of {{ and }} by setting the new values in JavaScript or in templates.

Setting in JavaScript

The Mustache.tags property holds an array consisting of the opening and closing tag values. Set custom values by passing a new array of tags to render(), which gets honored over the default values, or by overriding the Mustache.tags property itself:

1var customTags = [ '<%', '%>' ];

Pass Value into Render Method

1Mustache.render(template, view, {}, customTags);

Override Tags Property

1Mustache.tags = customTags;
2// Subsequent parse() and render() calls will use customTags

Setting in Templates

Set Delimiter tags start with an equals sign and change the tag delimiters from {{ and }} to custom strings.

Consider the following contrived example:

1* {{ default_tags }}
2{{=<% %>=}}
3* <% erb_style_tags %>
4<%={{ }}=%>
5* {{ default_tags_again }}

Here we have a list with three items. The first item uses the default tag style, the second uses ERB style as defined by the Set Delimiter tag, and the third returns to the default style after yet another Set Delimiter declaration.

According to ctemplates, this "is useful for languages like TeX, where double-braces may occur in the text and are awkward to use for markup."

Custom delimiters may not contain whitespace or the equals sign.

Pre-parsing and Caching Templates

By default, when mustache.js first parses a template it keeps the full parsed token tree in a cache. The next time it sees that same template it skips the parsing step and renders the template much more quickly. If you'd like, you can do this ahead of time using mustache.parse.

1Mustache.parse(template);
2
3// Then, sometime later.
4Mustache.render(template, view);

Command line tool

mustache.js is shipped with a Node.js based command line tool. It might be installed as a global tool on your computer to render a mustache template of some kind

1$ npm install -g mustache
2
3$ mustache dataView.json myTemplate.mustache > output.html

also supports stdin.

1$ cat dataView.json | mustache - myTemplate.mustache > output.html

or as a package.json devDependency in a build process maybe?

1$ npm install mustache --save-dev

1{
2  "scripts": {
3    "build": "mustache dataView.json myTemplate.mustache > public/output.html"
4  }
5}

1$ npm run build

The command line tool is basically a wrapper around Mustache.render so you get all the features.

If your templates use partials you should pass paths to partials using -p flag:

1$ mustache -p path/to/partial1.mustache -p path/to/partial2.mustache dataView.json myTemplate.mustache

Plugins for JavaScript Libraries

mustache.js may be built specifically for several different client libraries, including the following:

These may be built using Rake and one of the following commands:

1$ rake jquery
2$ rake mootools
3$ rake dojo
4$ rake yui3
5$ rake qooxdoo

TypeScript

Since the source code of this package is written in JavaScript, we follow the TypeScript publishing docs preferred approach by having type definitions available via @types/mustache.

Testing

In order to run the tests you'll need to install Node.js.

You also need to install the sub module containing Mustache specifications in the project root.

1$ git submodule init
2$ git submodule update

Install dependencies.

1$ npm install

Then run the tests.

1$ npm test

The test suite consists of both unit and integration tests. If a template isn't rendering correctly for you, you can make a test for it by doing the following:

Create a template file named mytest.mustache in the test/_files directory. Replace mytest with the name of your test.
Create a corresponding view file named mytest.js in the same directory. This file should contain a JavaScript object literal enclosed in parentheses. See any of the other view files for an example.
Create a file with the expected output in mytest.txt in the same directory.

Then, you can run the test with:

1$ TEST=mytest npm run test-render

Browser tests

Browser tests are not included in npm test as they run for too long, although they are ran automatically on Travis when merged into master. Run browser tests locally in any browser:

1$ npm run test-browser-local

then point your browser to http://localhost:8080/__zuul

Who uses mustache.js?

An updated list of mustache.js users is kept on the Github wiki. Add yourself or your company if you use mustache.js!

Contributing

mustache.js is a mature project, but it continues to actively invite maintainers. You can help out a high-profile project that is used in a lot of places on the web. No big commitment required, if all you do is review a single Pull Request, you are a maintainer. And a hero.

Your First Contribution

review a Pull Request
fix an Issue
update the documentation
make a website
write a tutorial

Thanks

mustache.js wouldn't kick ass if it weren't for these fine souls:

Chris Wanstrath / defunkt
Alexander Lang / langalex
Sebastian Cohnen / tisba
J Chris Anderson / jchris
Tom Robinson / tlrobinson
Aaron Quint / quirkey
Douglas Crockford
Nikita Vasilyev / NV
Elise Wood / glytch
Damien Mathieu / dmathieu
Jakub Kuźma / qoobaa
Will Leinweber / will
dpree
Jason Smith / jhs
Aaron Gibralter / agibralter
Ross Boucher / boucher
Matt Sanford / mzsanford
Ben Cherry / bcherry
Michael Jackson / mjackson
Phillip Johnsen / phillipj
David da Silva Contín / dasilvacontin

Stable Version

4.2.0

HIGH

6.1/10

Summary

Cross-Site Scripting in mustache

Affected Versions

< 2.2.1

Patched Versions

2.2.1

MODERATE

0/10

Summary

Moderate severity vulnerability that affects mustache

Affected Versions

< 2.2.1

Patched Versions

2.2.1

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

2

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:87: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:89: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:93: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:112: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:114: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:118: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:131: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/usage.yml:132: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:136: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:10: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:38: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:46: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:60: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:62: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/usage.yml:66: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/usage.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:68: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:72: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:76: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:10: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:44: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/verify.yml:52: update your workflow using https://app.stepsecurity.io/secureworkflow/janl/mustache.js/verify.yml/master?enable=pin
Warn: npmCommand not pinned by hash: .github/workflows/usage.yml:17
Warn: npmCommand not pinned by hash: .github/workflows/usage.yml:75
Warn: npmCommand not pinned by hash: .github/workflows/usage.yml:103
Warn: npmCommand not pinned by hash: .github/workflows/verify.yml:16
Warn: npmCommand not pinned by hash: .github/workflows/verify.yml:35
Warn: npmCommand not pinned by hash: .github/workflows/verify.yml:49
Warn: npmCommand not pinned by hash: .github/workflows/verify.yml:81
Info: 0 out of 28 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 1 third-party GitHubAction dependencies pinned
Info: 1 out of 8 npmCommand dependencies pinned

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Reason

107 existing vulnerabilities detected

Details

Warn: Project is vulnerable to: GHSA-6chw-6frg-f759
Warn: Project is vulnerable to: GHSA-v88g-cgmw-v5xw
Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
Warn: Project is vulnerable to: GHSA-fwr7-v2mv-hh25
Warn: Project is vulnerable to: GHSA-pp7h-53gx-mx7r
Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
Warn: Project is vulnerable to: GHSA-cwfw-4gq5-mrqx
Warn: Project is vulnerable to: GHSA-g95f-p29q-9xw4
Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
Warn: Project is vulnerable to: GHSA-x9w5-v3q2-3rhw
Warn: Project is vulnerable to: GHSA-wg6g-ppvx-927h
Warn: Project is vulnerable to: GHSA-rch9-xh7r-mqgw
Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
Warn: Project is vulnerable to: GHSA-92vm-wfm5-mxvv
Warn: Project is vulnerable to: GHSA-h452-7996-h45h
Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
Warn: Project is vulnerable to: GHSA-9vvw-cc9w-f27h
Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
Warn: Project is vulnerable to: GHSA-h6ch-v84p-w6p9
Warn: Project is vulnerable to: GHSA-vh7m-p724-62c2
Warn: Project is vulnerable to: GHSA-r9p9-mrjm-926w
Warn: Project is vulnerable to: GHSA-434g-2637-qmqr
Warn: Project is vulnerable to: GHSA-49q7-c7j4-3p7m
Warn: Project is vulnerable to: GHSA-977x-g7h5-7qgw
Warn: Project is vulnerable to: GHSA-f7q4-pwc6-w24p
Warn: Project is vulnerable to: GHSA-fc9h-whq2-v747
Warn: Project is vulnerable to: GHSA-gpvr-g6gh-9mc2
Warn: Project is vulnerable to: GHSA-cm5g-3pgc-8rg4
Warn: Project is vulnerable to: GHSA-jj78-5fmv-mv28
Warn: Project is vulnerable to: GHSA-rv95-896h-c2vc
Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
Warn: Project is vulnerable to: GHSA-9qj9-36jm-prpv
Warn: Project is vulnerable to: GHSA-8r6j-v8pm-fqw3
Warn: Project is vulnerable to: MAL-2023-462
Warn: Project is vulnerable to: GHSA-ww39-953v-wcq6
Warn: Project is vulnerable to: GHSA-qh2h-chj9-jffq
Warn: Project is vulnerable to: GHSA-q42p-pg8m-cqh6
Warn: Project is vulnerable to: GHSA-2cf5-4w76-r9qv
Warn: Project is vulnerable to: GHSA-3cqr-58rm-57f8
Warn: Project is vulnerable to: GHSA-g9r4-xpmj-mj65
Warn: Project is vulnerable to: GHSA-q2c6-c6pm-g3gh
Warn: Project is vulnerable to: GHSA-w457-6q6x-cgp9
Warn: Project is vulnerable to: GHSA-9prh-257w-9277
Warn: Project is vulnerable to: GHSA-765h-qjxv-5f44
Warn: Project is vulnerable to: GHSA-f2jv-r9rf-7988
Warn: Project is vulnerable to: GHSA-62gr-4qp9-h98f
Warn: Project is vulnerable to: GHSA-f52g-6jhx-586p
Warn: Project is vulnerable to: GHSA-jcpv-g9rr-qxrc
Warn: Project is vulnerable to: GHSA-44pw-h2cw-w3vq
Warn: Project is vulnerable to: GHSA-7f5c-rpf4-86p8
Warn: Project is vulnerable to: GHSA-vfrc-7r7c-w9mx
Warn: Project is vulnerable to: GHSA-jp4x-w63m-7wgm
Warn: Project is vulnerable to: GHSA-c429-5p7v-vgjp
Warn: Project is vulnerable to: GHSA-6x33-pw7p-hmpq
Warn: Project is vulnerable to: GHSA-qqgx-2p2h-9c37
Warn: Project is vulnerable to: GHSA-896r-f27r-55mw
Warn: Project is vulnerable to: GHSA-6c8f-qphg-qjgp
Warn: Project is vulnerable to: GHSA-jf85-cpcp-j695
Warn: Project is vulnerable to: GHSA-fvqr-27wr-82fm
Warn: Project is vulnerable to: GHSA-4xc9-xhrj-v574
Warn: Project is vulnerable to: GHSA-x5rq-j2xg-h7qm
Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
Warn: Project is vulnerable to: GHSA-p6mc-m468-83gw
Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
Warn: Project is vulnerable to: GHSA-wrvr-8mpx-r7pp
Warn: Project is vulnerable to: GHSA-hxm2-r34f-qmc5
Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
Warn: Project is vulnerable to: GHSA-vh95-rmgr-6w4m / GHSA-xvch-5gv4-984h
Warn: Project is vulnerable to: GHSA-3fx5-fwvr-xrjg
Warn: Project is vulnerable to: GHSA-w9mr-4mfr-499f
Warn: Project is vulnerable to: GHSA-7mc5-chhp-fmc3
Warn: Project is vulnerable to: GHSA-hj48-42vr-x3v9
Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
Warn: Project is vulnerable to: GHSA-rhx6-c78j-4q9w
Warn: Project is vulnerable to: GHSA-f9cm-p3w6-xvr3
Warn: Project is vulnerable to: GHSA-jjv7-qpx3-h62q
Warn: Project is vulnerable to: GHSA-gqgv-6jq5-jjj9
Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
Warn: Project is vulnerable to: GHSA-7xfp-9c55-5vqj
Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
Warn: Project is vulnerable to: GHSA-xwg4-93c6-3h42
Warn: Project is vulnerable to: GHSA-jgqf-hwc5-hh37
Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
Warn: Project is vulnerable to: GHSA-qg8p-v9q4-gh34
Warn: Project is vulnerable to: GHSA-g4rg-993r-mgx7
Warn: Project is vulnerable to: GHSA-4rq4-32rv-6wp6
Warn: Project is vulnerable to: GHSA-64g7-mvw6-v9qj
Warn: Project is vulnerable to: GHSA-8225-6cvr-8pqp
Warn: Project is vulnerable to: GHSA-3jfq-g458-7qm9
Warn: Project is vulnerable to: GHSA-r628-mhmh-qjhw
Warn: Project is vulnerable to: GHSA-9r2w-394v-53qc
Warn: Project is vulnerable to: GHSA-5955-9wpr-37jh
Warn: Project is vulnerable to: GHSA-qq89-hq3f-393p
Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
Warn: Project is vulnerable to: GHSA-xc7v-wxcw-j472
Warn: Project is vulnerable to: GHSA-34r7-q49f-h37c
Warn: Project is vulnerable to: GHSA-c9f4-xj24-8jqx
Warn: Project is vulnerable to: GHSA-v2p6-4mp7-3r9v
Warn: Project is vulnerable to: GHSA-6fc8-4gx4-v693
Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
Warn: Project is vulnerable to: GHSA-776f-qx25-q3cc

Score

2.7

/10

Last Scanned on 2024-12-16

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

Other packages similar to mustache

handlebars

4.7.8

Handlebars provides the power necessary to let you build semantic templates effectively with no frustration

@types/mustache

4.2.5

TypeScript definitions for mustache

hogan.js

3.0.2

A mustache compiler.

mustache-loader

1.4.3

Mustache loader for webpack