
Security News
CVE Volume Surges Past 48,000 in 2025 as WordPress Plugin Ecosystem Drives Growth
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.
jsmd ensures that you will never have outdated and non-working JavaScript code in your README files.
jsmd ensures that you will never have outdated and non-working code in your README files.
Usage: jsmd <path>
Options:
--show display the compiled JS after execution
--help display this help message
--version display the version number
Just write your README files in GitHub Flavored Markdown as usual. The only thing that you have to add is the actual assertions. So here is a small example that will hopefully illustrate how assertions look:
var fs = require('fs');
fs.unlink('/tmp/this-is-stupid', function(err) {
typeof err; // => 'object'
});
In this simple example we expect that the type of err is equal to 'object'.
As simple as that.
In order to verify if everything works properly just supply the desired file to jsmd and it will verify it for you:
$ jsmd README.md
See the examples for more info.
In order jsmd to recognize your JavaScript code elements, you have to specify them either as "js" or "javascript".
To get JavaScript syntax highlighting, without jsmd running the code, specify the code block as "node".
```node
var rm_rf = require('rimraf')
rm_rf('/usr/bin')
```
Sometimes you don't want to put helper code into your readme file, but it's necessary in order to perform the tests. In this case, you can simply add special html comments which jsmd will extract and put inside the compiled file.
<!-- js
var server = require('express');
server();
-->
That way, GitHub won't visualize the comment but jsmd will be able to parse it.
jsmd has very simple flow, that looks like this:
Math.min(1, 2) // => 1$ npm install jsmd -g
$ npm test
$ npm run-script coverage
Special thanks to:
(The MIT License)
Copyright (c) 2013 Veselin Todorov hi@vesln.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
jsmd ensures that you will never have outdated and non-working JavaScript code in your README files.
We found that jsmd demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.

Security News
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.