← Home

coffeelib

npm Repository Homepage

A tool to create isomorphic projects with CoffeeScript

19
Versions
0BSD
License
No
Install Scripts
Missing
Provenance

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

ch1c0t

Keywords

coffeescriptisomorphic

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:eval-usage AI (semgrep): eval() used as a template engine to render project scaffold files; input is local template content, not remote data. ai
semgrep semgrep:dynamic-require AI (semgrep): Loads helper modules from a known local subdirectory by filename; not user-controlled external input. ai
semgrep semgrep:child-process-import AI (semgrep): CLI scaffolding tool legitimately uses execSync to run git commands during project creation. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): 127.0.0.1 appears in a readme template as a localhost usage example, not an exfiltration endpoint. ai
phantom-deps phantom-dep:jasmine AI (phantom-deps): jasmine is a test runner declared as a runtime dep and used via config; phantom-dep heuristic false positive. ai
provenance no-provenance AI (provenance): Established package with 27 versions; lack of provenance is common and not a risk signal here. ai

Versions (showing 19 of 19)

Version Deps Published
0.6.9 8 / 0
0.6.8 8 / 0
0.6.7 8 / 0
0.6.6 8 / 0
0.6.5 8 / 0
0.6.4 8 / 0
0.6.3 8 / 0
0.6.2 8 / 0
0.6.1 6 / 2
0.6.0 6 / 2
0.5.7 6 / 2
0.5.6 6 / 2
0.5.5 6 / 2
0.5.4 6 / 2
0.5.3 6 / 2
0.5.2 6 / 2
0.5.1 6 / 2
0.5.0 5 / 2
0.4.0 5 / 1

v0.6.9

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.6.8

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.6.7

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.

v0.6.6

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.

v0.6.5

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.

v0.6.4

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.

v0.6.3

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.

v0.6.2

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.

v0.6.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.

v0.6.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.

v0.5.7

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.

v0.5.6

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.

v0.5.5

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.

v0.5.4

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.

v0.5.3

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.

v0.5.2

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.

v0.5.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.

v0.5.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.