escomplex-coffee
Software complexity analysis for CoffeeScript projects. CoffeeScript-specific wrapper around escomplex.
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): Publisher change from philbooth to addisonj occurred in 2015 (~10 years ago); addisonj has 96 approved packages and 0 rejected. Legitimate historical maintainer transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): addisonj added as maintainer in 2015 with strong track record (96/0). Stable historical transition, not a recent compromise signal. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop explained by removal of bundled coffee-script-redux in favor of npm-resolved coffee-script dependency. Not a stub/redirect. | ai |
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version was published by a different npm account than previous versions on 2015-02-23. 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.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.