volos-spikearrest-memory

v0.10.2

In-memory provider for Spike Arrest enforcement in the Volos system. For more information about how to use this package see README

Latest version published 5 years ago

License: MIT

NPM

GitHub

Package Health Score

58 / 100

security
No known security issues
popularity
Limited
maintenance
Inactive
community
Sustainable

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
0.10.2	\|	06/2019	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (154)

GitHub Stars: 205
Forks: 63
Contributors: 30

Direct Usage Popularity

The npm package volos-spikearrest-memory receives a total of 154 downloads a week. As such, we scored volos-spikearrest-memory popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package volos-spikearrest-memory, we found that it has been starred 205 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 30
Funding: No

With more than 10 contributors for the volos-spikearrest-memory repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like volos-spikearrest-memory is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 19
Open PR: 16
Last Release: 5 years ago
Last Commit: 10 days ago

Further analysis of the maintenance status of volos-spikearrest-memory based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for volos-spikearrest-memory is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 10 years
Dependencies: 2 Direct
Versions: 4
Install Size: 5.99 kB
Dist-tags: 1
# of Files: 4
Maintainers: 1
TS Typings: No

volos-spikearrest-memory has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

volos-quota-memory

This is a memory-backed implementation of Spike Arrest support for Volos.

Once initialized, the interface to the module is exactly what is in the "volos-spikearrest-common" module. See that module for detailed docs.

Initialization

To initialize a SpikeArrest, you call "create" on the exported module and pass a single "options" object. It can contain the following parameters:

timeUnit: How often the SpikeArrest resets - may be in seconds or minutes
allow: The maximum number of requests to allow during the timeUnit.
bufferSize: (optional, default = 0) if bufferSize > 0, SpikeArrest will attempt to smooth requests by returning only when the next appropriate execution window is available. bufferSize is how many requests to "queue" before returning (immediately) with a isAllowed = false.

Once the quota has been initialized, the module that is returned has the programming interface defined by the "volos-quota-common" module.

Example

var SpikeArrest = require('volos-spikearrest-memory');
var spikeArrest = SpikeArrest.create({
  timeUnit: 'second',
  allow: 10,
  bufferSize: 10
});

spikeArrest.apply({ key: 'Foo', weight: 1 }, function(err, result) {
  if (err) { throw err; }
  console.log('Status: %s', result.isAllowed);
});

volos-spikearrest-memory dependencies

debug volos-spikearrest-common

FAQs

What is volos-spikearrest-memory?

In-memory provider for Spike Arrest enforcement in the Volos system. Visit Snyk Advisor to see a full health score report for volos-spikearrest-memory, including popularity, security, maintenance & community analysis.

Is volos-spikearrest-memory popular?

The npm package volos-spikearrest-memory receives a total of 154 weekly downloads. As such, volos-spikearrest-memory popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is volos-spikearrest-memory well maintained?

We found indications that volos-spikearrest-memory is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is volos-spikearrest-memory safe to use?

The npm package volos-spikearrest-memory was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 23 April-2024, at 13:19 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP