Decode data. Browser or NodeJS.
Node addon for string extraction for msgpackr
Node addon for string extraction for cbor-x
Robustly get the byte length of a Typed Array
Streaming text decoder that preserves multibyte Unicode characters
Get the byte length of an ArrayBuffer, even in engines without a `.byteLength` method.
LEB128 utilities for Node
Robustly get the byte offset of a Typed Array
Get the byteOffset out of a DataView, robustly.
Get the byteLength out of a DataView, robustly.
WebAssembly binary format parser
base64 utilities for TypeScript and JavaScript
Get utf8 byte length of string
Reads / writes floats / doubles from / to buffers in both modern and ancient browsers.
Minimalist yEnc and dynEncode encoder and decoder library for browser and NodeJS
Sixel image format for node and browser.
Web Assembly streaming MPEG Layer I/II/III decoder
Convert a bytes or octets value (e.g. 34565346) to a human-readable string ('34.6 MB'). Choose between metric or IEC units.
Web Assembly streaming Opus decoder
A pure JavaScript implementation of a BPE tokenizer (Encoder/Decoder) for GPT-2 / GPT-3 / GPT-4 and other OpenAI models
A pure javascript BMP encoder and decoder
Web Assembly streaming Ogg Opus decoder
Utilities for encoding and decoding common formats like hex, base64, and varint. Ported from Deno's @std/encoding.
A pure TypeScript WebP encoder and decoder with zero native dependencies
Decodes Remove Nonstandard Utf8 Bytes-encoded files read by other file input plugins.
Enable encoding and decoding 4 byte chars - Emoji
Unicode characters are encoded into format `{{codepoint_hex}}` before being saved in db. For usage, please refer to the github page.
Functions include: big endian encode/decode, hex/bytes convert, keccak256 ...
Encode and decode hexadecimal strings with 0x prefix handling, produce xxd-style hex dumps, format hex output with configurable grouping, swap endianness, extract byte ranges, pad hex strings, convert between hex and integers, and validate hex strings.
EncodeM v3.0 brings complete M language (MUMPS) subscript encoding to Ruby, supporting numbers, strings, and composite keys with perfect sort order. Build hierarchical database keys like M("users", 42, "email") that sort correctly as raw bytes. This 40-year production-tested algorithm from YottaDB/GT.M powers Epic (70% of US hospitals) and VistA. Perfect for B-tree indexes, key-value stores, and any system requiring sortable hierarchical keys. All types maintain correct ordering when compared as byte strings - no decoding needed.
= The Owasp ESAPI Ruby project == Introduction The Owasp ESAPI Ruby is a port for outstanding release quality Owasp ESAPI project to the Ruby programming language. Ruby is now a famous programming language due to its Rails framework developed by David Heinemeier Hansson (http://twitter.com/dhh) that simplify the creation of a web application using a convention over configuration approach to simplify programmers' life. Despite Rails diffusion, there are a lot of Web framework out there that allow people to write web apps in Ruby (merb, sinatra, vintage) [http://accidentaltechnologist.com/ruby/10-alternative-ruby-web-frameworks/]. Owasp Esapi Ruby wants to bring all Ruby deevelopers a gem full of Secure APIs they can use whatever the framework they choose. == Why supporting only Ruby 1.9.2 and beyond? The OWASP Esapi Ruby gem will require at least version 1.9.2 of Ruby interpreter to make sure to have full advantages of the newer language APIs. In particular version 1.9.2 introduces radical changes in the following areas: === Regular expression engine (to be written) === UTF-8 support Unicode support in 1.9.2 is much better and provides better support for character set encoding/decoding * All strings have an additional chunk of info attached: Encoding * String#size takes encoding into account – returns the encoded character count * You can get the raw datasize * Indexed access is by encoded data – characters, not bytes * You can change encoding by force but it doesn’t convert the data === Dates and Time From "Programming Ruby 1.9" "As of Ruby 1.9.2, the range of dates that can be represented is no longer limited by the under- lying operating system’s time representation (so there’s no year 2038 problem). As a result, the year passed to the methods gm, local, new, mktime, and utc must now include the century—a year of 90 now represents 90 and not 1990." == Roadmap Please see ChangeLog file. == Note on Patches/Pull Requests * Fork the project. * Create documentation with rake yard task * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. == Copyright Copyright (c) 2011 the OWASP Foundation. See LICENSE for details.
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.