@abdulreal/flutterwave-node-v3

MITLicense declared in the package manifest.

The official Node.JS library for Flutterwave v3 payment APIs (patched for longer OTP support)

80

Security score

0 known advisories in v1.3.0-patch.1

OpenSSF Scorecard 3.3/10

0-100 score computed by this site from verifiable signals only: known OSV.dev advisories affecting this exact version, how recently it was published, and the repository's OpenSSF Scorecard.advisory penalty −0 · staleness penalty −0 · scorecard component 33/100 (30% weight)

Weekly downloads

Downloads across all versions in the last 7 days, from the official npm downloads API (api.npmjs.org).

6

Unpacked size

Size of v1.3.0-patch.1 on disk after npm install extracts the tarball, as reported by the npm registry.

490.4 kB

Dependencies

Direct runtime dependencies declared by v1.3.0-patch.1. Transitive dependencies are not counted here — use the lockfile audit for the full tree.

10

Last publish

When v1.3.0-patch.1 was published to the registry. Long gaps can indicate an unmaintained package.

11 months ago

Security advisories

Vulnerabilities affecting v1.3.0-patch.1 specifically, from OSV.dev — the open database aggregating the GitHub Advisory Database (GHSA) and CVEs. Links open the full advisory.

No known vulnerabilities affect v1.3.0-patch.1.

Downloads — last 30 days

Daily download counts across all versions for the last 30 days, from the npm downloads API. Weekend dips are normal for developer tooling.

50 total▼ 45.5% vs prior week

Jul 5Aug 3

OpenSSF ScorecardJul 27, 2026

OpenSSF Scorecard is an automated audit of the source repository's security practices, run by the Open Source Security Foundation. Each check scores 0-10; hover a check for what it means. Data via deps.dev.
  • MaintainedThe project shows recent activity: commits or issue triage within the last 90 days.Result: 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 55
  • Dangerous-WorkflowGitHub Actions workflows avoid dangerous patterns such as untrusted code checkout or script injection.Result: no dangerous workflow patterns detected10
  • Code-ReviewChanges are reviewed by another maintainer before landing on the main branch.Result: Found 1/12 approved changesets -- score normalized to 00
  • Token-PermissionsCI workflow tokens follow least privilege — read-only unless a job needs more.Result: detected GitHub workflow tokens with excessive permissions0
  • Binary-ArtifactsNo compiled binaries are committed to the repository — binaries can't be reviewed and may hide malicious code.Result: no binaries found in the repo10
  • Pinned-DependenciesBuild dependencies are pinned to exact versions or hashes, preventing silent supply-chain swaps.Result: dependency not pinned by hash detected -- score normalized to 00
  • CII-Best-PracticesThe project holds an OpenSSF Best Practices badge, a self-certification of security practices.Result: no effort to earn an OpenSSF best practices badge detected0
  • Security-PolicyA SECURITY.md explains how to report vulnerabilities privately.Result: security policy file not detected0
  • FuzzingThe project is fuzz-tested (e.g. OSS-Fuzz), which finds crashes and memory bugs automatically.Result: project is not fuzzed0
  • LicenseThe project publishes a license file.Result: license file detected10
  • Branch-ProtectionThe default branch is protected: force pushes are blocked and changes require review before merging.Result: branch protection not enabled on development/release branches0
  • SASTStatic analysis (e.g. CodeQL) runs on pull requests to catch bugs before merge.Result: SAST tool is not run on all commits -- score normalized to 00