co
generator async control flow goodness
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): The tjholowaychuk → jongleberry transition in Jan 2015 is a well-documented, legitimate maintainer handoff for the tj/co project. Not a compromise signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jonathanong and jongleberry were added as part of the documented 2015 maintainer transition from TJ Holowaychuk. Stable, legitimate change. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects the v3→v4 rewrite of co into a leaner library. No material changes between v4.0.2 and v4.2.0; not a stub/redirect. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): co is a long-established package; Levenshtein distance of 2 on a 2-char name is not meaningful as a typosquat signal. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): co is a long-established package; Levenshtein distance of 2 on a 2-char name is not meaningful as a typosquat signal. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): co is a long-established package; Levenshtein distance of 2 on a 2-char name is not meaningful as a typosquat signal. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): co is a long-established package; Levenshtein distance of 2 on a 2-char name is not meaningful as a typosquat signal. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): co is a long-established package (10+ years); short name triggers Levenshtein false positives against many 2-3 char packages. Not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): co is a long-established package; Levenshtein distance of 2 on a 2-char name is not meaningful as a typosquat signal. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): co is a long-established package; Levenshtein distance of 2 on a 2-char name is not meaningful as a typosquat signal. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 4.6.0 | 0 / 4 | |
| 4.5.4 | 0 / 4 | |
| 4.5.2 | 0 / 3 | |
| 4.5.1 | 0 / 3 | |
| 4.5.0 | 0 / 3 | |
| 4.4.0 | 0 / 3 | |
| 4.3.1 | 0 / 4 | |
| 4.3.0 | 0 / 4 | |
| 4.2.0 | 0 / 4 | |
| 4.1.0 | 0 / 4 | |
| 4.0.2 | 0 / 5 | |
| 4.0.1 | 0 / 5 | |
| 4.0.0 | 0 / 5 | |
| 3.1.0 | 0 / 6 | |
| 3.0.6 | 0 / 6 | |
| 3.0.5 | 0 / 6 | |
| 3.0.4 | 0 / 6 | |
| 3.0.2 | 0 / 6 | |
| 3.0.1 | 0 / 6 | |
| 3.0.0 | 0 / 6 | |
| 2.3.0 | 0 / 6 | |
| 2.2.0 | 0 / 6 | |
| 2.1.0 | 0 / 6 | |
| 2.0.0 | 0 / 6 | |
| 1.5.2 | 0 / 4 | |
| 1.5.1 | 0 / 4 | |
| 1.5.0 | 0 / 4 | |
| 1.4.1 | 0 / 3 | |
| 1.4.0 | 0 / 3 | |
| 1.3.0 | 0 / 3 | |
| 1.2.1 | 0 / 3 | |
| 1.2.0 | 0 / 3 | |
| 1.1.0 | 0 / 3 | |
| 1.0.0 | 0 / 2 |
v4.5.4
2 findingsThis version was published by a different npm account than previous versions on 2015-05-03. 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.
v4.5.2
2 findingsThis version was published by a different npm account than previous versions on 2015-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.
v4.5.1
2 findingsThis version was published by a different npm account than previous versions on 2015-03-18. 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.
v4.5.0
2 findingsThis version was published by a different npm account than previous versions on 2015-03-18. 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.
v4.4.0
2 findingsThis version was published by a different npm account than previous versions on 2015-02-15. 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.
v4.3.1
2 findingsThis version was published by a different npm account than previous versions on 2015-02-07. 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.
v4.3.0
2 findingsThis version was published by a different npm account than previous versions on 2015-02-07. 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.
v4.2.0
2 findingsThis version was published by a different npm account than previous versions on 2015-01-21. 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.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2014-12-26. 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.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.