rc-trigger 1.6.3

base abstract trigger component for react

rc-trigger@1.6.3 was published on 2016-07-08. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All rc-trigger versions · Permanent reference to 1.6.3 · Latest release

Package specifications

Version1.6.3
License declarationNot declared
Published2016-07-08T05:47:34.775Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entry./lib/index
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars391
Repository forks246

Install rc-trigger 1.6.3

npm install rc-trigger@1.6.3
pnpm add rc-trigger@1.6.3
yarn add rc-trigger@1.6.3

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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.

Code-Review1/10 — Found 5/26 approved changesets -- score normalized to 1
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions8/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy0/10 — security policy file not detected
SAST10/10 — SAST tool is run on all commits

Evidence and freshness