firebase

npm · Rank #178 of 217

88 / 100 B

STALE — No release in 5 days. Stale packages accumulate unpatched vulnerabilities.

npm publishers

Distributed credential risk

downloads/week

Blast radius if compromised

14.3y

package age

Established package

5 days ago

last release

Active maintenance

GitHub contributors

Source code contributors

— Provenance Not enabled

— Staged Publishing Not enabled

⚠️ Dormant Access 3 inactive publishers with npm access

Risk analysis

firebase has not published a release in over 12 months. Stale packages accumulate vulnerabilities and may indicate abandonment.

Publisher depth — How many people can push to npm? Single-publisher packages are the #1 structural risk.
Longevity — Older packages have track records. New packages with high adoption are higher risk.
Release consistency — Regular releases signal active oversight. Long gaps mean unpatched vulnerabilities.
Download trend — Growing packages attract more scrutiny (and more attacks).
OpenSSF Scorecard — Process security: branch protection, code review, CI/CD safety.
Build provenance — Published versions linked to specific CI runs via SLSA attestation.
Staged publishing — Human approval gate between npm publish and going live.

You came looking for firebase. Your node_modules has hundreds more. Run one command to score every dependency you ship:

npx proof-of-commitment

Auto-detects your lockfile. Scores every dependency. Zero install.