open-index/open-npm huggingface dataset:
npm package: @standardnotes/authenticator
Description: As of version 2.0, TokenVault houses a public-source, but not open-source presence. This means you are free to browse the code and even use the code _privately_, but you may not redistribute, repackage, or otherwise use its public distributable/release as
Author: Standard Notes
Latest version: 2.4.13

## LICENSE

As of version 2.0, TokenVault houses a public-source, but not open-source presence. This means you are free to browse the code and even use the code _privately_, but you may not redistribute, repackage, or otherwise use its public distributable/release assets on GitHub, for free or for profit.

For more information, read [this blog post](https://blog.standardnotes.com/why-tokenvault-is-going-public-source/).

Previous versions of TokenVault retain the license they were released with.
npm package: @standardnotes/component-relay
Description: To get started using the Component Relay, read the [Intro to Extensions guide](https://docs.standardnotes.org/extensions/intro).
Latest version: 2.2.2

# Component Relay

To get started using the Component Relay, read the [Intro to Extensions guide](https://docs.standardnotes.org/extensions/intro).

## Installation

```
yarn add @standardnotes/component-relay
```

&dash; _or_ &dash;

```
npm install --save @standardnotes/component-relay
```

### Manual

Import the file `dist/dist.js` in your HTML file. For example:

```html
...
<script type="text/javascript" src="dist/dist.js"></script>
...
```

## Tests

The `component-relay` uses [Jest](https://jestjs.io/) for tests. Tests are located in the [test](test) directory. Test files have the following name: `<name>.test.js`.

### Run all tests

Run `yarn test` or `npm test` to run all test suites.

### Coverage

Coverage can be generated by running the `coverage` script.

Then open the [coverage/index.html](coverage/index.html) file in a browser to view it.

## Documentation

Documentation is generated using [Typedoc](https://typedoc.org/). The documentation is available at https://standardnotes.github.io/component-relay/. To update the docs or to view the latest version, run:

```
yarn build:docs
```

This will generate documentation and place it in the `docs/` directory. Create a localhost server using `http-server` and open the [docs/index.html](docs/index.html) file in a browser to view the docs.

To deploy the latest version of the docs to the `gh-pages` branch to publish using [GitHub Pages](https://pages.github.com/), replace `2.0.1` with the latest version and run:

```
yarn deploy-docs -m "build: v2.0.1"
```
npm package: @standardnotes/components
Description: Packaging a component will create a zip archive of dist assets, compute a checksum, and create a release on GitHub and upload the custom zip archive.
Author: Standard Notes
Latest version: 1.9.1

## Packaging Components

Packaging a component will create a zip archive of dist assets, compute a checksum, and create a release on GitHub and upload the custom zip archive.

Note that checksums are based on the resulting zip archive, and that re-zipping the same files results in a different checksum. It is imperative that once checksums are computed, the respective .zip file is used as the distributable.

If a release already exists on GitHub, packaging will be skipped.

**Important:** Be sure to have `GH_TOKEN` exported in your env in order for the GitHub CLI tool to function properly.

### Package all components:

```
yarn run package-components
```

### Package single component:

```
yarn run package-components org.standardnotes.code-editor
```

### Releasing an update to a component:

1. Bump the version of the feature in `snjs/packages/features/src/Domain/Feature/Features.ts`
2. Run `yarn build` inside `snjs/packages/features`
3. Bump the version of the component in `snjs/packages/components/package.json`
4. Run `yarn run package-components org.standardnotes.feature-identifier`
npm package: @standardnotes/decrypt
Description: As part of our mission to keep your data safe for the next hundred years, we want to ensure you have the right tools to handle worst-case scenarios.
Latest version: 1.1.6

## Offline

As part of our mission to keep your data safe for the next hundred years, we want to ensure you have the right tools to handle worst-case scenarios.

The encryption algorithms involved in securing your data are completely open-source and non-proprietary, so you don't have to rely on us for your data to be safe and valid.

To further your protections against general disruptions in your network or ours, we've created a single page offline decryption tool that can run in any browser.

### Decrypting a Backup Offline

[Download the offline decrypt script](https://raw.githubusercontent.com/standardnotes/snjs/master/packages/decrypt/dist/decrypt.html) and open it with any browser.

You can right click the link above and choose "Save link as", or open the page directly and save the page with Cmd/Ctrl + S.

_Always make sure you get this script from a trusted source, such as our website._

### Creating Backups

There are two ways to create backups of your note data:

1. Manual: In the "Account" menu of the Standard Notes app, in the lower left corner, you will see options for downloading encrypted or decrypted archives of your data.

2. Automatic: [Our Extended subscription](https://standardnotes.com/extensions) creates automatic and real-time backups of all your data to your Dropbox, OneDrive, and Google Drive, with other cloud providers being added soon.

#### Need help? We're here for you.

Find some frequently asked questions as well as ways to get in touch on the [Help](https://standardnotes.com/help) page.

## Building the script yourself

This script was built with [Node.js](https://nodejs.org/) v14. Make sure it is installed on your system.
Then, in the repo, run the following commands:

1. `yarn install`
2. `yarn run build`

(You can replace `yarn` with `npm` if you want)


This will output a new `dist/decrypt.html` file.