Deno mini-port of @mozillasecurity/octo
Find a file
2018-01-22 22:32:03 +01:00
deploy Re-add octo.js for distribution w/ jsdelivr. 2017-06-12 15:08:10 -04:00
lib Add range generator for floating points 2018-01-16 18:39:48 +01:00
tests Modify random.item to work with array-like objects and update tests 2017-07-20 15:29:37 -04:00
.editorconfig Add .editorconfig 2017-04-23 02:29:16 +03:00
.gitignore Ignore .idea project files 2017-04-25 11:03:38 -04:00
.jshintrc Add random to .jshintrc 2017-04-13 16:17:33 +03:00
.travis.yml Deploy to both github pages (always) & releases (tagged) 2017-06-07 12:34:17 -04:00
build.py Use Travis CI to automate build and deploy. 2017-06-07 11:42:09 -04:00
Gruntfile.js Add pre-commit hook for standard linter 2018-01-22 22:30:40 +01:00
karma.conf.js Add pre-commit hook for standard linter 2018-01-22 22:30:40 +01:00
LICENSE Add LICENSE 2017-04-22 23:09:22 +03:00
package.json Add pre-commit hook for standard linter 2018-01-22 22:32:03 +01:00
README.md Update README.md 2017-08-08 12:47:06 +02:00

Logo

Build Status Coverage Status JavaScript Style
Guide IRC Current Release Downloads

Octo.js is a unified shared library which aids in building fuzzers for browsers or as complement for an already existing fuzzing framework.

It 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 is a stable, well-tested and well-documented standard library for fuzzing in a JavaScript environment.

Usage

<!-- Latest -->
https://mozillasecurity.github.io/octo/octo.js

<!-- Release -->
https://github.com/mozillasecurity/octo/releases/download/0.1/octo.js

Development

./build.py -l lib -d deploy

Testing

Tests live in the tests/ subdirectory, and are written for QUnit. To run tests locally, open tests/index.html in a browser. The automated tests are run in Firefox or Chrome using Karma. To run the automated tests:

npm install
CHROME_BIN=chromium npm test

When adding new files, add them in index.html and karma.conf.js so they can be tested and included in coverage reports.