@atlassian-test-staging/synth-check
This repository contains the synthetic checks for the Artifactory Forwarder service.
npm says
195,758
per week
Every tarball fetch: mirrors, scanners, CI and people.
real installs
high confidence≈ 186K–188K
per week
best guess 187K
Mirror spikes and crawlers removed. CI and dependency installs still count, so this is not a head count.
About 5% of npm's count looks like noise. noise real installs
Why this estimate
With JavaScript on, this lists what the filter found for this package.
Snapshot from the daily build of Nov 10, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use @atlassian-test-staging/synth-check?
npm counted 195,758 downloads of @atlassian-test-staging/synth-check in the last 7 days. Nobody can count people exactly, npm included: it does not record who downloaded what. After removing mirror spikes and crawlers, about 186K–188K look like real installs. Noise is 5% of npm's count. What remains still includes CI and installs as a dependency of other packages.
Is @atlassian-test-staging/synth-check still maintained?
Most likely yes, going by its releases. The latest version, 1.0.130308, came out on Nov 10, 2026. The last 12 months saw 31,965 stable releases, typically 1 day apart, plus 1 pre-release. It was first published on Dec 9, 2025. npm lists 1 maintainer.
Is @atlassian-test-staging/synth-check still used?
Downloads with publish spikes removed are up 89% over 3 months. Last week, 100% of downloads above the crawler floor were on major version 1, the latest one; the most used single version was 1.0.129764, with 0%. Weekdays get 0.78× the downloads of weekends, so there is no clear work-week rhythm. Over the last 12 months, 208,577 downloads arrived in publish spikes and were attributed to mirrors. Crawlers account for about 8,909 downloads a week, roughly 1 per version.
Monthly downloads of @atlassian-test-staging/synth-check
The busiest month was Oct 2026, with about 26,156 downloads a day once publish spikes are removed; the quietest was Jan 2026, with about 7,074.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 680,055 | 0 | 646K–652K | about flat |
| Sep 2026 | 706,209 | 0 | 671K–677K | up 8% |
| Aug 2026 | 959,927 | 208,577 (22%) | 714K–929K | up 110% |
| Jul 2026 | 357,215 | 0 | 339K–343K | down 7% |
| Jun 2026 | 372,468 | 0 | 354K–357K | up 11% |
| May 2026 | 347,104 | 0 | 330K–333K | up 26% |
| Apr 2026 | 266,949 | 0 | 254K–256K | up 17% |
| Mar 2026 | 236,384 | 0 | 225K–227K | about flat |
| Feb 2026 | 208,406 | 0 | 198K–200K | up 5% |
| Jan 2026 | 219,298 | 0 | 208K–210K | — |
Whole months through Oct 31, 2026. Publish spikes are found day by day and summed per month. Real installs apply this week's crawler share to each month's downloads (the upper end also keeps the removed spikes), so they follow npm's curve rather than measure it. The change compares spike-free downloads per day.
How the estimate works
- Cut the spike every new version gets from mirrors in its first days.
- Subtract the flat floor robots download from every version each week.
- Show what is left as a range, with a confidence level. It still includes CI and dependency installs, so it is not a count of people.