Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
rehype-minify-json-script
Advanced tools
rehype plugin to minify `script` elements with a JSON body
rehype plugin to minify JSON <script>
s.
This package is a plugin that can minify the contents of JSON <script>
s:
<script>
elements with (currently) a type of application/ld+json
.
You can use this plugin when you want to improve the size of HTML documents.
This package is ESM only. In Node.js (version 16+), install with npm:
npm install rehype-minify-json-script
In Deno with esm.sh
:
import rehypeMinifyJsonScript from 'https://esm.sh/rehype-minify-json-script@4'
In browsers with esm.sh
:
<script type="module">
import rehypeMinifyJsonScript from 'https://esm.sh/rehype-minify-json-script@4?bundle'
</script>
On the API:
import rehypeMinifyJsonScript from 'rehype-minify-json-script'
import rehypeParse from 'rehype-parse'
import rehypeStringify from 'rehype-stringify'
import {read} from 'to-vfile'
import {unified} from 'unified'
const file = await unified()
.use(rehypeParse)
.use(rehypeMinifyJsonScript)
.use(rehypeStringify)
.process(await read('index.html'))
console.log(String(file))
On the CLI:
rehype input.html --use rehype-minify-json-script --output output.html
On the CLI in a config file (here a package.json
):
…
"rehype": {
"plugins": [
…
+ "rehype-minify-json-script",
…
]
}
…
This package exports no identifiers.
The default export is rehypeMinifyJsonScript
.
unified().use(rehypeMinifyJsonScript)
Minify JSON <script>
s.
Transform (Transformer
).
<script type="application/ld+json">
{
"@context": {
"name": "http://xmlns.com/foaf/0.1/name",
"@id": "http://me.example.com",
"@type": "Person",
"name": "John Smith",
"homepage": "http://www.example.com/"
}
}
</script>
<script type="application/ld+json">{"@context":{"name":"John Smith","@id":"http://me.example.com","@type":"Person","homepage":"http://www.example.com/"}}</script>
HTML is parsed according to WHATWG HTML (the living standard), which is also followed by all browsers.
The syntax tree used is hast.
This package is fully typed with TypeScript.
Projects maintained by the unified collective are compatible with maintained versions of Node.js.
When we cut a new major release, we drop support for unmaintained versions of
Node.
This means we try to keep the current release line,
rehype-minify-json-script@^4
,
compatible with Node.js 16.
As rehype works on HTML and improper use of HTML can open you up to a
cross-site scripting (XSS) attack, use of rehype can also be unsafe.
Use rehype-sanitize
to make the tree safe.
See contributing.md
in rehypejs/.github
for ways
to get started.
See support.md
for ways to get help.
This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.
FAQs
rehype plugin to minify `script` elements with a JSON body
The npm package rehype-minify-json-script receives a total of 8,419 weekly downloads. As such, rehype-minify-json-script popularity was classified as popular.
We found that rehype-minify-json-script demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.