@midwayjs/cos MIT 19 versions

@midwayjs/cos

npm Repository Homepage

midway cos component

19

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

czy88840616legendecasechosoarlellansinlxxyxstone-jinmariodu

Keywords

tencentcos

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:cors	AI (typosquat): Legitimate MidwayJS COS (Cloud Object Storage) component; not a typosquat of cors.	ai	2026/04/28
typosquat	typosquat.levenshtein:koa	AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to koa is coincidental.	ai	2026/04/28
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to got is coincidental.	ai	2026/04/28
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to qs is coincidental.	ai	2026/04/28
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to joi is coincidental.	ai	2026/04/28
typosquat	typosquat.levenshtein:zod	AI (typosquat): Scoped MidwayJS framework package; Levenshtein match to zod is coincidental.	ai	2026/04/28
bogus-package	bogus-package	AI (bogus-package): Monorepo sub-package; minimal README is expected for framework components.	ai	2026/04/28

Versions (showing 19 of 119)

Version	Deps	Published
3.2.1	1 / 4	2022-03-27
3.2.0	1 / 4	2022-03-25
3.1.6	1 / 4	2022-03-21
3.1.5	1 / 4	2022-03-18
3.1.2	1 / 4	2022-03-15
3.1.1	1 / 4	2022-03-09
3.1.0	1 / 4	2022-03-07
3.0.13	1 / 4	2022-03-01
3.0.11	1 / 4	2022-02-25
3.0.10	1 / 4	2022-02-24
3.0.9	1 / 4	2022-02-21
3.0.7	1 / 4	2022-02-17
3.0.6	1 / 4	2022-02-13
3.0.5	1 / 4	2022-02-10
3.0.4	1 / 4	2022-02-09
3.0.3	1 / 4	2022-01-28
3.0.2	1 / 4	2022-01-24
3.0.1	1 / 4	2022-01-24
3.0.0	1 / 4	2022-01-20

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.6

1 finding

LOW No provenance attestation provenance

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

v3.1.5

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.13

1 finding

LOW No provenance attestation provenance

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

v3.0.11

1 finding

LOW No provenance attestation provenance

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

v3.0.10

1 finding

LOW No provenance attestation provenance

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

v3.0.9

1 finding

LOW No provenance attestation provenance

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

v3.0.7

1 finding

LOW No provenance attestation provenance

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

v3.0.6

1 finding

LOW No provenance attestation provenance

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

v3.0.5

1 finding

LOW No provenance attestation provenance

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

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

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