← Home

@coko/server

npm Repository

Reusable server for use by Coko's projects

7
Versions
MIT
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

yannisbarlasalexgeorg86

Keywords

coko

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/express AI (phantom-deps): TypeScript type package; not directly imported but required for compilation. ai
phantom-deps phantom-dep:@types/passport AI (phantom-deps): TypeScript type package; not directly imported but required for compilation. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require used to load migration files by path — standard migration runner pattern. ai
typosquat typosquat.levenshtein:semver AI (typosquat): Scoped package @coko/server from Coko Foundation with 145 versions; not a typosquat of semver. ai
phantom-deps phantom-dep:graphql AI (phantom-deps): graphql is listed as a direct dependency in package.json; phantom-dep false positive. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in image processing module alongside sharp — expected for image manipulation. ai
semgrep semgrep:base64-decode AI (semgrep): Decoding a base64-encoded CA certificate for SSL DB connection config — standard pattern, not malicious. ai

Versions (showing 7 of 7)

Version Deps Published
5.1.0 64 / 19
5.0.0 64 / 19
4.22.0 57 / 8
4.21.1 57 / 8
4.21.0 57 / 8
4.20.0 57 / 8
4.19.0 57 / 8

v5.1.0

1 finding
LOW No provenance attestation provenance

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

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.22.0

1 finding
LOW No provenance attestation provenance

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

v4.21.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@coko/server' is 1 edit(s) away from popular package 'semver'.

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.

v4.21.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@coko/server' is 1 edit(s) away from popular package 'semver'.

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.

v4.20.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@coko/server' is 1 edit(s) away from popular package 'semver'.

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.

v4.19.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@coko/server' is 1 edit(s) away from popular package 'semver'.

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.