@codixus/mt
Cross-platform skill manager + dev shortcut CLI
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:got | AI (typosquat): Scoped package @codixus/mt; Levenshtein match to short names is noise, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @codixus/mt; Levenshtein match to short names is noise, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @codixus/mt; Levenshtein match to short names is noise, not impersonation. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.3.4 | 5 / 4 | |
| 0.3.3 | 5 / 4 | |
| 0.3.1 | 5 / 4 | |
| 0.3.0 | 5 / 4 | |
| 0.2.10 | 5 / 4 | |
| 0.2.8 | 5 / 4 | |
| 0.2.6 | 5 / 4 | |
| 0.2.5 | 5 / 4 | |
| 0.2.4 | 5 / 4 | |
| 0.2.3 | 5 / 4 | |
| 0.2.2 | 5 / 4 | |
| 0.2.1 | 5 / 4 | |
| 0.1.1 | 5 / 4 |
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.