get user in json genered random
Random utility functions for ethers.
Generates an id useable in json rpc payloads.
Package for formatting JSON data in a coloured YAML-style, perfect for CLI output
Generate random numbers from various distributions.
TypeScript definitions for d3-random
Fastest random ID and random string generation for Node.js
URL and cookie safe UIDs
Find and load configuration from a package.json property, rc file, TypeScript module, and more!
Use the random function in CSS
An alias package for `crypto.randomBytes` in Node.js and/or browsers
A utility to work with tsconfig.json without typescript
Generate a cryptographically strong random string
A JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for current web browsers and node.js-based servers
Docusaurus theme translations.
A Pulumi package to safely use randomness in Pulumi programs.
Configuration file loader for @rushstack/heft
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.
Generate a random integer
Statistical routines and probability distributions.
Provides functions for detecting if the host environment supports the WebCrypto API
Random JSON generation, structured JSON by schema generation, no dependencies.
Wallet management utilities for KeyStore and Crowdsale JSON wallets.
Creating Electron app packages
This gem returns simple JSON/hash responses from the Random User Generator API.
This gem returns simple JSON/hash responses from the Russian Random User Generator API.
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.