@golemio/mos
Golemio Mos Module
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 | |
| typosquat | typosquat.levenshtein:mobx | AI (typosquat): Scoped @golemio package; Levenshtein match to 'mobx' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @golemio package; Levenshtein match to 'got' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @golemio package; Levenshtein match to 'cors' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @golemio package; Levenshtein match to 'qs' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @golemio package; Levenshtein match to 'joi' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @golemio package; Levenshtein match to 'zod' is coincidental. | ai | |
| phantom-deps | phantom-dep:JSONStream | AI (phantom-deps): JSONStream is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 1 / 34 | |
| 1.1.24 | 1 / 34 | |
| 1.1.23 | 1 / 34 | |
| 1.1.22 | 1 / 34 | |
| 1.1.21 | 1 / 34 | |
| 1.1.20 | 1 / 34 | |
| 1.1.19 | 1 / 34 | |
| 1.1.18 | 1 / 34 | |
| 1.1.17 | 1 / 34 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.