usage-stats — Greenflagged

A minimal, offline-friendly Google Analytics Measurement Protocol client for tracking statistics in shell and javascript applications

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

75lb

Keywords

googleanalyticsmeasurementprotocoltrackingusagestatsappapplicationga

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:silent-process-exec	AI (semgrep): Finding is in tmp/fork-experiment.js, a developer scratch file not part of the package runtime. Stable false positive for this package.	ai	2026/04/24
semgrep	semgrep:silent-process-exec-var	AI (semgrep): Finding is in tmp/fork-experiment.js, a developer scratch file not part of the package runtime. Stable false positive for this package.	ai	2026/04/24
semgrep	semgrep:child-process-spawn	AI (semgrep): Finding is in tmp/fork-experiment.js, a developer scratch file not part of the package runtime. Stable false positive for this package.	ai	2026/04/24
npm-metadata	suspicious-initial-version	AI (npm-metadata): 0.0.0 is the legitimate initial version of this long-established package from a trusted publisher with 1414 approved packages. Not a throwaway malicious package.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): child_process is used for environment/capability detection (execSync with ENOENT fallback), consistent with a CLI analytics tool. Not malicious.	ai	2026/04/24
source-diff	large-new-source-files	AI (source-diff): Large number of new files explained by addition of es5/ transpilation output directory via babel build step added in this version.	ai	2026/04/24

Versions (showing 35 of 35)

Version	Deps	Published
0.9.5	6 / 3	2023-01-16
0.9.4	6 / 4	2017-07-10
0.9.3	6 / 4	2017-06-26
0.9.2	6 / 4	2017-06-26
0.9.1	6 / 4	2017-05-14
0.9.0	6 / 4	2017-02-10
0.8.6	9 / 6	2017-06-04
0.8.5	9 / 6	2017-05-06
0.8.4	9 / 6	2017-05-06
0.8.3	9 / 6	2017-05-06
0.8.2	9 / 6	2016-11-23
0.8.1	9 / 6	2016-11-08
0.8.0	9 / 6	2016-11-01
0.7.0	11 / 6	2016-09-29
0.6.0	11 / 6	2016-09-20
0.5.0	11 / 6	2016-09-17
0.4.4	11 / 6	2016-09-01
0.4.3	11 / 6	2016-08-31
0.4.2	11 / 6	2016-08-31
0.4.1	11 / 6	2016-08-30
0.4.0	11 / 6	2016-08-28
0.3.2	10 / 6	2016-08-24
0.3.1	6 / 6	2016-08-23
0.3.0	6 / 6	2016-08-23
0.2.1	6 / 5	2016-08-17
0.2.0	6 / 5	2016-08-17
0.1.5	5 / 4	2016-08-12
0.1.4	5 / 4	2016-08-11
0.1.3	5 / 4	2016-08-08
0.1.2	4 / 2	2016-08-08
0.1.1	4 / 1	2016-08-08
0.1.0	4 / 1	2016-08-08
0.0.2	3 / 1	2016-08-07
0.0.1	2 / 0	2016-08-07
0.0.0	1 / 0	2016-08-07

v0.9.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.4

3 findings

HIGH silent-process-exec: tmp/fork-experiment.js:3 semgrep

Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/75lb/usage-stats/blob/10ff36cb3d54d14a963262320a14fdf781418c13/tmp/fork-experiment.js#L3 1 | const cp = require('child_process') 2 | > 3 | const child = cp.spawn('node', [ 'spam-files.js' ], { 4 | detached: true, 5 | stdio: 'ignore'

HIGH silent-process-exec-var: tmp/fork-experiment.js:3 semgrep

Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/75lb/usage-stats/blob/10ff36cb3d54d14a963262320a14fdf781418c13/tmp/fork-experiment.js#L3 1 | const cp = require('child_process') 2 | > 3 | const child = cp.spawn('node', [ 'spam-files.js' ], { 4 | detached: true, 5 | stdio: 'ignore'

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

3 findings

HIGH silent-process-exec: tmp/fork-experiment.js:3 semgrep

Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/75lb/usage-stats/blob/e904034daddb38f5941653a80154483f42498578/tmp/fork-experiment.js#L3 1 | const cp = require('child_process') 2 | > 3 | const child = cp.spawn('node', [ 'spam-files.js' ], { 4 | detached: true, 5 | stdio: 'ignore'

HIGH silent-process-exec-var: tmp/fork-experiment.js:3 semgrep

Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/75lb/usage-stats/blob/e904034daddb38f5941653a80154483f42498578/tmp/fork-experiment.js#L3 1 | const cp = require('child_process') 2 | > 3 | const child = cp.spawn('node', [ 'spam-files.js' ], { 4 | detached: true, 5 | stdio: 'ignore'

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.2

3 findings

HIGH silent-process-exec: tmp/fork-experiment.js:3 semgrep

Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/75lb/usage-stats/blob/e2e840a531faaa84c806df8b5ffef59c682b9123/tmp/fork-experiment.js#L3 1 | const cp = require('child_process') 2 | > 3 | const child = cp.spawn('node', [ 'spam-files.js' ], { 4 | detached: true, 5 | stdio: 'ignore'

HIGH silent-process-exec-var: tmp/fork-experiment.js:3 semgrep

Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/75lb/usage-stats/blob/e2e840a531faaa84c806df8b5ffef59c682b9123/tmp/fork-experiment.js#L3 1 | const cp = require('child_process') 2 | > 3 | const child = cp.spawn('node', [ 'spam-files.js' ], { 4 | detached: true, 5 | stdio: 'ignore'

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.