Deno mini-port of @mozillasecurity/octo
Find a file
2019-12-11 16:08:05 -08:00
lib Skip failing test at TravisCI 2018-09-18 04:26:29 +02:00
.editorconfig Add .editorconfig 2017-04-23 02:29:16 +03:00
.gitignore Update .travis.yml 2018-09-18 04:22:03 +02:00
.travis.yml Fix what 'travis setup release' destroyed 2018-09-18 05:26:11 +02:00
CODE_OF_CONDUCT.md Add Mozilla Code of Conduct file 2019-03-30 10:49:59 -07:00
index.js Add linter fixes 2018-03-19 05:54:40 +01:00
LICENSE Add LICENSE 2017-04-22 23:09:22 +03:00
package.json Update package dependencies 2019-12-11 13:46:42 -05:00
README.md Update README.md 2018-09-18 18:22:17 +02:00
yarn.lock Yet another yarn.lock update after running yarn upgrade. 2019-12-11 16:08:05 -08:00

Logo

A unified shared library which aids in building fuzzers for browsers or as complement for an already existing fuzzing framework.

JavaScript Style Guide Build Status Current Release Coverage Status Dependencies Status Dev Dependencies Status IRC

Octo.js bundles core functions and generic boilerplate code commonly used in most frameworks for fuzzing browsers. It is designed for the sharing of improvements between our individual fuzzers, and with the purpose of reducing the maintainability of those core features with minimal effort.

Octo's future aims to be a stable, well-tested and well-documented standard library for fuzzing in a JavaScript environment.

Table of Contents

Playbook

https://npm.runkit.com/@mozillasecurity/octo

Usage in Node

yarn add @mozillasecurity/octo
const { random, make } = require("@mozillasecurity/octo");
random.init();

// Common Operations
make.number.any();
make.text.any();

// WebCrypto
make.crypto.randomAlgorithm();

// WebGL
make.webgl.randomSamplerParameter();

Take a look into the API documentation for further use cases.

Usage in the Browser

yarn install
yarn build

A bundled production build (octo.js) is placed into the local dist directory.

Development

yarn lint
yarn test
yarn build

Testing

Octo.js uses Jest for testing. Each directory should contain a __tests__ folder containing the tests.

yarn test

API Documentation

or

yarn docs

What do the developers say?