A random Json Data Generator
Random JSON generator for mock service
A random json generator
Statistical routines and probability distributions.
A small implementation of `crypto.getRandomValues` for React Native. This is useful to polyfill for libraries like [uuid](https://www.npmjs.com/package/uuid) that depend on it.
CSV and object generation implementing the Node.js `stream.Readable` API
An alias package for `crypto.randomBytes` in Node.js and/or browsers
Random number generator using xorshift128+
Generates an id useable in json rpc payloads.
Generate JSON schema from your Typescript sources
Universal Module for Secure Random Generator in JavaScript
A tiny (118 bytes), secure URL-friendly unique string ID generator
Changes JsonValues to your custom typescript type
Meteor's Random Package for Straight Node
Generate unique and memorable names
Mersenne twister pseudorandom number generator
JSON schema generator based on draft-v4.
> Monorepo of isomorphic utility functions
A very basic crypto library
A functional typescript implementation of the PCG family random number generators
GRC's UHE PRNG in node (Ultra-High Entropy Pseudo-Random Number Generator by Gibson Research Corporation)
Fractional index library with jittering and generator
Pseudo-random number generators w/ unified API, distributions, weighted choices, ID generation
random data generator for when test data is insignificant
generate random json string
Generate random data based on your JSON schemas
This gem returns simple JSON/hash responses from the Random User Generator API.
Generates random yes/no gifs in json format
This gem returns simple JSON/hash responses from the Russian Random User Generator API.
Andor is a simple name generator based on an 'And/Or' JSON format. It includes simple examples of generating random fake movie preview descriptions, 'mad science' compounds and British town names.
The middleware makes sure any request to specified paths would have been preflighted if it was sent by a browser. We don't want random websites to be able to execute actual GraphQL operations from a user's browser unless our CORS policy supports it. It's not good enough just to ensure that the browser can't read the response from the operation; we also want to prevent CSRF, where the attacker can cause side effects with an operation or can measure the timing of a read operation. Our goal is to ensure that we don't run the context function or execute the GraphQL operation until the browser has evaluated the CORS policy, which means we want all operations to be pre-flighted. We can do that by only processing operations that have at least one header set that appears to be manually set by the JS code rather than by the browser automatically. POST requests generally have a content-type `application/json`, which is sufficient to trigger preflighting. So we take extra care with requests that specify no content-type or that specify one of the three non-preflighted content types. For those operations, we require one of a set of specific headers to be set. By ensuring that every operation either has a custom content-type or sets one of these headers, we know we won't execute operations at the request of origins who our CORS policy will block.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.