read from /dev/urandom or another random number source device
read random levelup values
read random facts right from your terminal while waiting
Generates an id useable in json rpc payloads.
Generate random numbers from various distributions.
Unzip cross-platform streaming API
TypeScript definitions for d3-random
Fastest random ID and random string generation for Node.js
RFC9562 UUIDs
URL and cookie safe UIDs
Easily make random-access-storage instances
Use the random function in CSS
A tiny (118 bytes), secure URL-friendly unique string ID generator
An alias package for `crypto.randomBytes` in Node.js and/or browsers
Isomorphic Library for Random Bytes
Generate a cryptographically strong random string
Random utility functions for ethers.
A Pulumi package to safely use randomness in Pulumi programs.
Provides functions for detecting if the host environment supports the WebCrypto API
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.
Currents CLI tools
Continuous reading or writing to a file using random offsets and lengths
Simple Reading and Writing of Random Access Files
Pickpocket: selects a random article from your Pocket (former Read It Later)
RandomJpg is a tool for easy downloading random images for use in scripts, application test data etc. It runs silently in the background feeding random images to a named pipe at a specified location, by default /tmp/random.jpg.
MtgHand gives you a random starting hand, by reading a CSV file of your decklist
This simple gem generates a random password that is easy to read and remember. It uses dictionary words as well as a list of proper names mixed in with numbers and special characters.
scbi_ace is a ruby gem to read and parse ACE files containing contigs. It automatically indexes the input ace file to improve random access to contigs.
Xelor was built for systems that require random bytes for processes faster than one second. Because normal random generation is based off of time as a seed, if there exists multiple calls towards SecureRandom or Rand within one second, the same number will be produced. This can be resolved on unix or linux based systems by making a system call to read /dev/urandom.
A library for working with LC/MS runs. Part of mspire. Has parsers for mzXML v1, 2, and 3, mzData (currently broken) and mzML (planned). Can convert to commonly desired search output (such as mgf). Fast random access of scans, and fast reading of the entire file.
I/O pipeline construction framework. Allows to construct data processing pipelines in a manner of UNIX shell pipes. Implemented features: string splitting/merging, IO or local file reading/writing, FTP/SFTP file reading/writing, digest computing, Gzip/Zlib (de)compression, Zstd (de)compression, symmetric cipher (de,en)cryption, random data generation.
Generate user-friendly, pseudo-random codes without ambiguous letters or numbers (e.g. 0 vs O vs o). For scenarios where only computers will be interacting, this is probably the way to go. But when the interaction involves a human, we want to remove ambigouity to improve accessibility and ease of reading and entering data. Use cases: * Entering code sent via SMS into a web page or app * Entering code from printed material into a web page or app
Random Poetry Scraper is a command line gem which returns a configurable number of poems scraped from poemhunter.com. The gem allows you to consume the poems either through a JSON dump or through a command line "pleasure reading" interface. ~Most~ poems on poemhunter.com are in English, but not all are. If you plan to to use this gem to build a corpus of poetry, you should do additional language validation.
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.
No description provided.
No description provided.