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

rake-pos

v1.0.17

Published

A typescript implementation of the Rapid Automated Keyword Extraction (RAKE) algorithm with Part-of-Speech post-processing

Downloads

256

Readme

rake-pos: Rapid automatic keyword extraction with Part-of-Speech post-processing

The goal of this library was to create a Typescript translation of the javacsript implementation, which in itself was a translation of the python implementation.

Extraction defaults to processing the input text as if it is written in the English language. Stop words are provided by default using stopwords-iso

In addition, Part-of-Speech post-processing is used to further filter keywords. This is done by using an implementation of brill tagging. For usage details, see the list of brill tag descriptions

Basic Usage


let keywords: string[] = [];
console.log(keywords);
> []

const input: string = 'I have some apples and bananas here for the table';
keywords = extractWithRakePos({ text: input });
console.log(keywords);
> ['table', 'bananas', 'apples']

const stop: Set<string> = new Set(['apples']);
keywords = extractWithRakePos({ text: input, additionalStopWordSet: stop });
console.log(keywords);
> ['table', 'bananas']

Original README from javacsript implementation below:

Differences in regular expressions and stopword lists have big impacts on this algorithm and sticking close to the python means that the code was easy to compare to ensure that it was in the ballpark.

This algorithm is described in Text Mining: Applications and Theory and also in this excellent blog post by Alyona Medelyan.

It operates using only the text you give it and produces surprisingly good results. There are likely better results possible but these mostly seem to involve a combination of Python, Machine Learning and a corpus of data.

The appeal of RAKE is of the "bang for the buck" variety.

Currently this library produces subtly different results than either the paper or the original Python implementation. While the results (especially the top scoring ones) line up nicely, these little deviations represent something to understand and resolve.

What's next

After hammering out differences in the results, plans are to focus on

  • Fully embracing JS idioms (Promises/ES201X)
  • Explore ways to improve the results as described here
  • Options to control result format (number, result|result+rank, etc)
  • Include default stopword list.
  • Improve handling of special characters and italics
  • Deal with sentences that have been split over multiple lines (sentence now ends with -)

Stopword lists

The stopword list used by the python version is here. It has a comment as the first line which might break the world...

Links to other stopword lists can be found here

Any file with one word per line should be fine.