@rctflw/background 11.0.0-next.0

Background component with different variants for React Flow

@rctflw/background@11.0.0-next.0 was published on 2022-08-29. Its manifest declares 3 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @rctflw/background versions · Permanent reference to 11.0.0-next.0 · Latest release

Package specifications

Version11.0.0-next.0
License declarationMIT
Published2022-08-29T10:19:25.957Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size15.26 KiB
Published file count11
Package typeNot declared
ES module entrydist/rctflw-background.esm.js
Default entrydist/rctflw-background.cjs.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies2
Repository stars38809
Repository forks2561

Install @rctflw/background 11.0.0-next.0

npm install @rctflw/background@11.0.0-next.0
pnpm add @rctflw/background@11.0.0-next.0
yarn add @rctflw/background@11.0.0-next.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
Code-Review2/10 — Found 2/9 approved changesets -- score normalized to 2
Maintained10/10 — 30 commit(s) and 22 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST6/10 — SAST tool is not run on all commits -- score normalized to 6

Evidence and freshness