npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

remark-encrypted-block

v0.0.1

Published

This plugin parses custom Markdown syntax to create an encrypted block that gets rendered into an script tag.

Downloads

3

Readme

remark-encrypted-block

This plugin parses custom Markdown syntax to create an encrypted block that gets rendered into an script tag.

Usage is pretty basic, just add a link pointing to #!encrypt and everything after will be encrypted using node-rsa and rendered to base64.

Syntax

This will not be encrypted.
[\#!encrypt]()
This will be encrypted.
Also this.

produces:

<p>This will not be encrypted</p>
<script type="application/base64" integrity="sha256-${cyphertext hash}">
...base64 cyphertext...
</script>

You need to configure by setting a public key string (format pkcs1-public-pem) under the configuration object key named key.

{
  key: '-----BEGIN RSA PUBLIC KEY-----${pubKey}-----END RSA PUBLIC KEY-----'
}

Installation

npm:

npm install --save remark-encrypted-block

Usage

Dependencies:

const unified = require('unified')
const remarkParse = require('remark-parse')
const stringify = require('rehype-stringify')
const remark2rehype = require('remark-rehype')

const remarkCustomBlocks = require('remark-custom-blocks')

Usage:

unified()
  .use(remarkParse)
  .use(remarkEncryptedBlock, {
    key: '-----BEGIN RSA PUBLIC KEY-----${pubKey}-----END RSA PUBLIC KEY-----'
  })
  .use(remark2rehype)
  .use(stringify)

The sample configuration provided above would have the following effect:

  1. Allows you to use the following Markdown syntax to define the beginning of the encrypted block:

    This will not be encrypted.
    [\#!encrypt]()
    This will be encrypted.
    Also this.
  2. This Remark plugin would create a mdast node for the encrypted block, this node would be of type:

    • encryptedBlock
  3. If you're using rehype, you will end up with a script like this:

  <script type="application/base64" integrity="sha256-${cyphertext hash}">
  ...base64 cyphertext...
  </script>

License

ISC

Links