line — Greenflagged

Control flow like a boss

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

amccollum

Keywords

enderflowcontrolasync

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:vite	AI (typosquat): 'line' is a 14-year-old generic control-flow library predating 'vite' by many years; Levenshtein proximity is coincidental and not a typosquat.	ai	2026/04/24
typosquat	typosquat.levenshtein:pino	AI (typosquat): 'line' is a 14-year-old generic control-flow library; Levenshtein proximity to 'pino' is coincidental and not a typosquat.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package is ~14 years old; provenance attestation was not available at publish time and is not expected for packages of this vintage.	ai	2026/04/24

Versions (showing 12 of 12)

Version	Deps	Published
0.1.8	1 / 2	2013-02-18
0.1.7	1 / 2	2013-02-01
0.1.6	0 / 2	2013-02-01
0.1.5	0 / 2	2012-10-21
0.1.4	0 / 2	2012-10-03
0.1.3	0 / 2	2012-09-26
0.1.2	0 / 2	2012-09-04
0.1.1	0 / 2	2012-02-22
0.1.0	0 / 2	2012-02-18
0.0.3	0 / 2	2012-02-15
0.0.2	0 / 2	2012-02-15
0.0.1	0 / 2	2012-02-12

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

INFO No provenance attestation provenance

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

v0.1.6

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

INFO No provenance attestation provenance

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

v0.1.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] 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

INFO No provenance attestation provenance

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

v0.1.0

1 finding

INFO No provenance attestation provenance

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

v0.0.3

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

INFO No provenance attestation provenance

[Accepted risk] 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. Only ~12% of npm packages have provenance, so this is common but not ideal.