chore: add missing npm engine constraint to stats/base/dists/*/ctor

[Planeshifter]

Description

Adds the missing "npm": ">2.7.0" entry to the engines field in the package.json of every distribution-constructor package under @stdlib/stats/base/dists/*/ctor. All 34 ctor packages specified only "node": ">=0.10.0" while 5,418 of 5,469 (99.07%) @stdlib/* packages specify both node and npm engines. Root cause is template-copy drift in the distribution-constructor scaffold.

Changes

Applied a uniform edit to 34 files — one package.json per distribution constructor:

   "engines": {
-    "node": ">=0.10.0"
+    "node": ">=0.10.0",
+    "npm": ">2.7.0"
   },

Packages updated (34):

arcsine, bernoulli, beta, betaprime, binomial, cauchy, chi, chisquare, cosine, degenerate, discrete-uniform, erlang, exponential, f, frechet, gamma, geometric, gumbel, hypergeometric, invgamma, kumaraswamy, laplace, levy, logistic, lognormal, negative-binomial, normal, pareto-type1, poisson, rayleigh, t, triangular, uniform, weibull.

No behavior, signatures, tests, or docs are affected. The diff on every file is identical (+2 / -1).

How this was found

A majority-vote drift pass over the 14 members of @stdlib/stats/base/dists/uniform flagged uniform/ctor as missing the npm engine constraint (13/14 = 93% conformance within the namespace). A follow-up codebase-wide audit over 5,469 @stdlib/* packages revealed the same drift across every stats/base/dists/*/ctor package — a template-copy pattern:

engines shape	Count
{"node": ">=0.10.0", "npm": ">2.7.0"}	5,418
{"node": ">=0.10.0"} ← drift	34
Other (non-standard node constraint, all include npm)	18

All 34 offenders are stats/base/dists/*/ctor packages; no other namespace exhibits the drift.

Related Issues

None.

Questions

None.

Other

The uniform namespace drift routine also surfaced uniform/mgf as missing the "probability" keyword (13/14 siblings within the namespace). A cross-distribution check revealed only 2 of 21 other stats/base/dists/*/mgf packages (cosine, degenerate) include "probability" — the uniform namespace convention appears to be a local template-copy, not a cross-distribution norm. That correction was dropped from this PR.

Checklist

• Read, understood, and followed the contributing guidelines.

AI Assistance

• Yes
• No

Used AI assistance for:

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

This PR was authored end-to-end by Claude Code running a cross-package API drift detection routine, extended with a codebase-wide audit of the engines field. The scope expanded from one package (uniform/ctor) to 34 after discovery that the drift pattern covered every stats/base/dists/*/ctor package. All changes are identical, mechanical package.json edits with no behavioral impact; maintainer audit still recommended before promoting out of draft.

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

No coverage information available.