npm Package Version Delta Monitor avatar

npm Package Version Delta Monitor

Pricing

from $1.00 / 1,000 new npm package versions

Go to Apify Store
npm Package Version Delta Monitor

npm Package Version Delta Monitor

Monitors public npm packages for new versions via the official registry API and emits only deltas. First run baselines without charging. PPE event: version-delta.

Pricing

from $1.00 / 1,000 new npm package versions

Rating

0.0

(0)

Developer

Collin Reynolds

Collin Reynolds

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 hours ago

Last modified

Share

Watch public npm packages for new versions via the official registry API (registry.npmjs.org). Only deltas since the last run are written to the dataset — ideal for dependency monitoring, SBOM/ops agents, and scheduled changelogs.

Pricing (pay per event): $0.001 per version-delta (each newly detected package version). Actor start is a small platform event (~$0.00005). First run baselines quietly (0 dataset items / 0 delta charges) so you are not billed for history.

Why use this

  • API-only — official npm registry JSON (no HTML scraping)
  • Delta-only — subsequent runs emit new versions only
  • First-run safe — empty state seeds LAST_SEEN with zero PPE delta charges
  • No auth required for public packages
  • Schedule-friendly — pair with an Apify schedule for continuous monitoring
  • Scoped packages supported (@scope/name)

Input

FieldRequiredDescription
packagesyesList of npm package names (incl. scoped)
sinceVersionnoOn first run for a package, treat this version and older (by publish time) as already seen
includePrereleasesnoInclude semver prereleases (default true)
resetStatenoClear LAST_SEEN and re-baseline (0 emits that run)

Example

{
"packages": ["lodash", "axios", "@apify/utilities"],
"includePrereleases": true,
"resetState": false
}

Output

Each dataset item is a newly detected version, for example:

  • package, version, published_at, package_description, is_prerelease, is_latest, registry_url, tarball_url

First-run behavior

SituationDataset itemsversion-delta charges
Empty state, no sinceVersion00 (baseline only)
Empty state + sinceVersionOnly newer than that version1 per item
Later runsNew version strings only1 per item

Tips

  1. Run once to baseline, then attach a schedule (e.g. hourly/daily).
  2. Keep package lists focused — each packument fetch is one HTTP GET.
  3. Set a user max total charge on the run so costs stay predictable.

ToS / scope

Uses the public npm registry REST API only. See ./AGREEMENT.md. Respect npm registry terms and fair use.