@impactor/gcloud-storagenpm

Verdict

Not enough signal to judge

We could not find enough public signal to judge @impactor/gcloud-storage — no repository resolved from its registry metadata.

health 59/100

Why this verdict?

unknown — No repository resolved from the registry metadata, and no recent release either.

no repository resolved from registry metadata; last release 157 days ago

Judged 11 days ago from signal heuristics. How each verdict is decided

latest 6.0.0
last known licence MIT
assessment attempted 11 days ago
registry checked 17 days ago
registry ↗
repository ↗

Vulnerabilities, end of life and next steps

Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.

Review remediation options →

Maintenance trends

Loading historical repository activity…

Signals · last 2 checks

Commits 90d

—

Open issues

—

Unanswered

—

Contributors

—

What the project says about itself

Build provenance — the latest release carries no provenance attestation. Source: the registry.
Supported runtime — node ^18.19.1 || ^20.11.1 || >=22.0.0. Source: the registry.
Publishers on the registry — 1. Source: the registry.
Funding — paypal.me/group99001, www.patreon.com/GoogleDev. Source: the registry.

Third-party facts checked 11 days ago; registry facts on every crawl.

State history 1

When	Change
2026-11-01	first verdict: unknown

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/npm/@impactor/gcloud-storage.svg)](https://isitdeadyet.dev/npm/@impactor/gcloud-storage)

Watch it

Get told when @impactor/gcloud-storage changes state, changes licence, or is deprecated — instead of finding out during an incident.

Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.