View @cycle/history on Snyk Open Source Advisor

Package Health Score

63 / 100

security
No known security issues
popularity
Small
maintenance
Inactive
community
Active

Security

No known security issues

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

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
9.0.0	\|	12/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
8.0.0	\|	02/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
7.4.0	\|	11/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
6.10.0	\|	11/2017		0 C 0 H 0 M 0 L	0 H 0 M 0 L
6.9.0	\|	11/2017		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

Small

Weekly Downloads (273)

GitHub Stars: 10.24K
Forks: 419
Contributors: 120

Direct Usage Popularity

The npm package @cycle/history receives a total of 273 downloads a week. As such, we scored @cycle/history popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @cycle/history, we found that it has been starred 10,243 times.

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

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 120
Funding: Yes

A good and healthy external contribution signal for @cycle/history project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 77
Open PR: 25
Last Release: 3 years ago
Last Commit: 12 months ago

Further analysis of the maintenance status of @cycle/history 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 @cycle/history 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.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

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: 9 years
Dependencies: 3 Direct
Versions: 41
Install Size: 88.6 kB
Dist-tags: 2
# of Files: 48
Maintainers: 3
TS Typings: Yes

@cycle/history 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.

Not sure how to use @cycle/history?

To help you get started, we've collected the most common ways that @cycle/history is being used within popular public projects.

Cmdv / cycle-webpack-boilerplate / src / __test__ / main.spec.js View on Github

test('Main component tests', function(t) {
  t.plan(3);
  // mock the Main component and pass it the sources
  function mainComponent(sources) {
    let requests = Main(sources)
    return requests
  }

  // Pass Main through our RenderTarget
  let {sinks, sources} = run(mainComponent, {
    DOM: makeDOMDriver(createRenderTarget()),
    History: makeHistoryDriver({
      hash: false,
      queries: true,
    }),
  });
  // take our sources.Dom and select a class from it then subscribe and start testing against the results
  sources.DOM.select('.pure-g').observable.skip(1).take(1).subscribe(function (el) {

    t.equal(Array.isArray(el), true, 'Our subscription output is an array');
    const childrenEls = el[0].childNodes;
    t.equal(childrenEls[0].className, "sidebar pure-u-1 pure-u-md-1-4", "the first node should be the sidebar");
    t.equal(childrenEls[1].className, "content pure-u-1 pure-u-md-3-4", "the second node should be the content");
  });
});

View more ways to use @cycle/history

@cycle/history dependencies

@cycle/run history xstream

@cycle/history development dependencies

@cycle/rxjs-run @types/mocha @types/node @types/sinon deepmerge karma karma-browserstack-launcher karma-chrome-launcher karma-firefox-launcher karma-mocha karma-typescript mocha rxjs sinon ts-node tslint typescript xstream

FAQs

What is @cycle/history?

The standard history driver for Cycle.js. Visit Snyk Advisor to see a full health score report for @cycle/history, including popularity, security, maintenance & community analysis.

Is @cycle/history popular?

The npm package @cycle/history receives a total of 273 weekly downloads. As such, @cycle/history popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @cycle/history well maintained?

We found indications that @cycle/history is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is @cycle/history safe to use?

The npm package @cycle/history 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 11 November-2024, at 13:27 (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

@cycle/history

The standard history driver for Cycle.js For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (273)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use @cycle/history?

@cycle/history dependencies

@cycle/history development dependencies

FAQs

What is @cycle/history?

Is @cycle/history popular?

Is @cycle/history well maintained?

Is @cycle/history safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (273)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use @cycle/history?

@cycle/history dependencies

@cycle/history development dependencies

FAQs

What is @cycle/history?

Is @cycle/history popular?

Is @cycle/history well maintained?

Is @cycle/history safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues