foreground-child
Run a child as if it's the foreground process. Give it stdio. Exit when it exits.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from bcoe to isaacs (original author, tapjs org maintainer). Legitimate maintainer context; isaacs is the package author. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Major version rewrite to TypeScript with dual CJS/ESM dist output explains the size increase. No suspicious content. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 1 / 8 | |
| 4.0.2 | 1 / 8 | |
| 4.0.1 | 1 / 8 | |
| 4.0.0 | 1 / 8 | |
| 3.3.1 | 2 / 8 | |
| 3.3.0 | 2 / 8 | |
| 3.2.1 | 2 / 8 | |
| 3.2.0 | 2 / 8 | |
| 3.1.1 | 2 / 9 | |
| 3.1.0 | 2 / 9 | |
| 3.0.0 | 2 / 9 | |
| 2.0.0 | 2 / 1 | |
| 1.5.6 | 2 / 1 | |
| 1.5.5 | 2 / 1 | |
| 1.5.4 | 2 / 1 | |
| 1.5.3 | 2 / 1 | |
| 1.5.2 | 2 / 1 | |
| 1.5.1 | 3 / 1 | |
| 1.5.0 | 3 / 1 | |
| 1.4.0 | 3 / 1 | |
| 1.3.5 | 3 / 1 | |
| 1.3.4 | 2 / 1 | |
| 1.3.3 | 2 / 1 | |
| 1.3.1 | 2 / 1 | |
| 1.3.0 | 1 / 1 | |
| 1.2.0 | 1 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.0 | 0 / 1 |
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-04-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.