← Home

@midwayjs/cos

npm Repository Homepage

midway cos component

10
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

czy88840616legendecasechosoarlellansinlxxyxstone-jinmariodu

Keywords

tencentcos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Legitimate MidwayJS COS (Cloud Object Storage) component; not a typosquat of cors. ai
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to koa is coincidental. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to got is coincidental. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to qs is coincidental. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to joi is coincidental. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to zod is coincidental. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; minimal README is expected for framework components. ai

Versions (showing 10 of 10)

Version Deps Published
4.1.0 1 / 3
4.0.3 1 / 3
4.0.2 1 / 3
4.0.1 1 / 3
4.0.0 1 / 3
3.20.24 1 / 3
3.20.23 1 / 3
3.20.22 1 / 3
3.20.19 1 / 3
3.20.11 1 / 3

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.3

1 finding
LOW No provenance attestation provenance

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

v4.0.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.

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.20.23

1 finding
LOW No provenance attestation provenance

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

v3.20.22

1 finding
LOW No provenance attestation provenance

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

v3.20.19

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.

v3.20.11

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.