npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

bruteforcer

v1.0.1

Published

Enumerating all possible candidates for a problem to find the solution

Downloads

4

Readme

Bruteforcer

Enumerating all possible candidates for a problem to find the solution.

Installation

$ npm install bruteforcer

Usage

First we create a Bruteforcer, giving it characters, length limit and a callback. After that all we need to do is start(). Check every candidate in the callback and return true when the problem is sovled.

let Bruteforcer = require('bruteforcer');

let bf = new Bruteforcer({
  chars: 'abc',
  min: 1,
  max: 2,
  cbk: (str, caseIdx, caseNum) => {
    console.log('Trying', str);
    
    if ('ca' == str) {
      console.log('We got it!');
      return true;
    }
    else {
      return false;
    }
  }
});

bf.start();

Options

These are keys in the config object you can pass to the Bruteforcer along with.

  • chars characters(a string or an array of strings) to generate candidates.
  • min (optional)minimum length of the candidate, default is 1.
  • max (optional)maximum length of the candidate, default is 1.
  • cbk (optional) a callback to check every candidate. It is called with three parameters: candidate, caseIndex and caseNum. Return "true" to stop the enumerating.

Note

When passing the chars option with an array of strings, it means that you want to generate the candidate using each charset in the array orderly and at least once.

new Bruteforcer({
  chars: ['abc', '123'],
  min: 3,
  max: 3,
  cbk: chkResult
  });

// "ab3" is a candidate
// "31a" is not a candidate
// "123" is not a candidate
// "abc" is not a candidate

API

Following APIs are provided as well:

startFrom(caseIndex)

To start enumerating with specified caseIndex which you can get by calling getCaseIndex(). You may use it to restore previous session.

stop()

Another way to terminate the enumerating.

setCallback(callback)

Set the callback at a later time.

getCaseIndex()

Get the current case index among all cases.

getCaseNumber()

Get the total number of cases.

License

MIT License.