@golemio/mos MIT 35 versions

@golemio/mos

npm Repository Homepage

Golemio Mos Module

35

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

sinacekbenaktomoict-robot

Keywords

golemio

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:koa	AI (typosquat): Scoped @golemio package; Levenshtein match to 'koa' is coincidental, not impersonation.	ai	2026/04/29
typosquat	typosquat.levenshtein:mobx	AI (typosquat): Scoped @golemio package; Levenshtein match to 'mobx' is coincidental.	ai	2026/04/29
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped @golemio package; Levenshtein match to 'got' is coincidental.	ai	2026/04/29
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped @golemio package; Levenshtein match to 'cors' is coincidental.	ai	2026/04/29
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped @golemio package; Levenshtein match to 'qs' is coincidental.	ai	2026/04/29
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @golemio package; Levenshtein match to 'joi' is coincidental.	ai	2026/04/29
typosquat	typosquat.levenshtein:zod	AI (typosquat): Scoped @golemio package; Levenshtein match to 'zod' is coincidental.	ai	2026/04/29
phantom-deps	phantom-dep:JSONStream	AI (phantom-deps): JSONStream is a declared runtime dependency; phantom-dep heuristic misfires here.	ai	2026/04/29

Versions (showing 35 of 35)

Version	Deps	Published
1.3.0	1 / 34	2026-07-14
1.2.0	1 / 34	2026-06-02
1.1.24	1 / 34	2026-04-28
1.1.23	1 / 34	2026-03-17
1.1.22	1 / 34	2026-02-12
1.1.21	1 / 34	2026-01-15
1.1.20	1 / 34	2026-01-09
1.1.19	1 / 34	2025-09-02
1.1.18	1 / 34	2025-08-21
1.1.17	1 / 34	2025-06-10
1.1.16	1 / 34	2024-12-03
1.1.15	1 / 34	2024-11-28
1.1.13	1 / 34	2024-07-04
1.1.12	1 / 35	2024-05-13
1.1.11	1 / 35	2023-12-06
1.1.10	1 / 35	2023-08-30
1.1.9	1 / 35	2023-08-23
1.1.8	1 / 35	2023-08-07
1.1.7	1 / 34	2023-07-24
1.1.6	1 / 32	2023-06-14
1.1.5	1 / 31	2023-05-31
1.1.4	1 / 31	2023-05-29
1.1.3	1 / 31	2023-05-03
1.1.2	1 / 31	2023-03-13
1.1.1	1 / 31	2023-02-27
1.1.0	1 / 31	2023-01-23
1.0.9	1 / 31	2022-11-29
1.0.8	1 / 31	2022-11-18
1.0.7	1 / 31	2022-09-21
1.0.6	1 / 32	2022-06-21
1.0.5	1 / 32	2022-01-06
1.0.4	1 / 32	2021-09-01
1.0.3	1 / 32	2021-07-26
1.0.2	1 / 32	2021-05-11
1.0.0	1 / 32	2021-03-26

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.1.16

1 finding

LOW No provenance attestation provenance

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

v1.1.15

1 finding

LOW No provenance attestation provenance

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

v1.1.13

1 finding

LOW No provenance attestation provenance

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

v1.1.12

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.

v1.1.11

1 finding

LOW No provenance attestation provenance

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

v1.1.10

1 finding

LOW No provenance attestation provenance

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

v1.1.9

1 finding

LOW No provenance attestation provenance

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

v1.1.8

1 finding

LOW No provenance attestation provenance

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

v1.1.7

1 finding

LOW No provenance attestation provenance

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

v1.1.6

1 finding

LOW No provenance attestation provenance

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

v1.1.5

1 finding

LOW No provenance attestation provenance

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

v1.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

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

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