@team-semicolon/semo-cli
SEMO CLI - AI Agent Orchestration Framework Installer
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
Versions (showing 100 of 106)
| Version | Deps | Published |
|---|---|---|
| 4.18.20 | 7 / 10 | |
| 4.18.19 | 7 / 10 | |
| 4.18.18 | 7 / 10 | |
| 4.18.17 | 7 / 10 | |
| 4.18.16 | 7 / 10 | |
| 4.18.15 | 7 / 10 | |
| 4.18.12 | 7 / 10 | |
| 4.18.11 | 7 / 10 | |
| 4.18.10 | 7 / 9 | |
| 4.18.9 | 7 / 9 | |
| 4.18.8 | 7 / 9 | |
| 4.18.7 | 7 / 9 | |
| 4.18.6 | 7 / 9 | |
| 4.18.5 | 7 / 9 | |
| 4.18.4 | 7 / 9 | |
| 4.18.3 | 8 / 9 | |
| 4.18.0 | 6 / 8 | |
| 4.17.0 | 6 / 8 | |
| 4.16.0 | 5 / 8 | |
| 4.15.1 | 5 / 8 | |
| 4.15.0 | 5 / 8 | |
| 4.13.0 | 5 / 5 | |
| 4.12.0 | 5 / 5 | |
| 4.11.0 | 5 / 5 | |
| 4.10.0 | 5 / 5 | |
| 4.9.0 | 5 / 5 | |
| 4.8.0 | 5 / 5 | |
| 4.7.4 | 5 / 5 | |
| 4.7.3 | 5 / 5 | |
| 4.7.2 | 5 / 5 | |
| 4.7.0 | 5 / 5 | |
| 4.6.2 | 5 / 5 | |
| 4.6.0 | 5 / 5 | |
| 4.4.3 | 5 / 5 | |
| 4.4.2 | 5 / 5 | |
| 4.4.1 | 5 / 5 | |
| 4.4.0 | 5 / 5 | |
| 4.3.0 | 5 / 5 | |
| 4.2.0 | 5 / 5 | |
| 4.1.5 | 5 / 5 | |
| 4.1.4 | 5 / 5 | |
| 4.1.3 | 5 / 5 | |
| 4.1.1 | 5 / 5 | |
| 4.1.0 | 5 / 5 | |
| 4.0.5 | 5 / 5 | |
| 4.0.4 | 5 / 5 | |
| 4.0.3 | 5 / 5 | |
| 4.0.2 | 5 / 5 | |
| 4.0.1 | 5 / 5 | |
| 4.0.0 | 5 / 5 | |
| 3.14.1 | 5 / 5 | |
| 3.14.0 | 5 / 5 | |
| 3.13.1 | 5 / 4 | |
| 3.13.0 | 5 / 4 | |
| 3.12.0 | 5 / 4 | |
| 3.10.0 | 4 / 4 | |
| 3.9.0 | 4 / 4 | |
| 3.8.1 | 4 / 4 | |
| 3.7.4 | 4 / 4 | |
| 3.7.3 | 4 / 4 | |
| 3.7.2 | 4 / 4 | |
| 3.7.1 | 4 / 4 | |
| 3.7.0 | 4 / 4 | |
| 3.6.0 | 4 / 4 | |
| 3.5.0 | 4 / 4 | |
| 3.4.0 | 4 / 4 | |
| 3.3.0 | 4 / 4 | |
| 3.2.0 | 4 / 4 | |
| 3.1.0 | 4 / 4 | |
| 3.0.31 | 4 / 4 | |
| 3.0.30 | 4 / 4 | |
| 3.0.29 | 4 / 4 | |
| 3.0.28 | 4 / 4 | |
| 3.0.27 | 4 / 4 | |
| 3.0.26 | 4 / 4 | |
| 3.0.23 | 4 / 4 | |
| 3.0.22 | 4 / 4 | |
| 3.0.21 | 4 / 4 | |
| 3.0.20 | 4 / 4 | |
| 3.0.19 | 4 / 4 | |
| 3.0.18 | 4 / 4 | |
| 3.0.17 | 4 / 4 | |
| 3.0.16 | 4 / 4 | |
| 3.0.15 | 4 / 4 | |
| 3.0.14 | 4 / 4 | |
| 3.0.13 | 4 / 4 | |
| 3.0.12 | 4 / 4 | |
| 3.0.11 | 4 / 4 | |
| 3.0.10 | 4 / 4 | |
| 3.0.9 | 4 / 4 | |
| 3.0.7 | 4 / 4 | |
| 3.0.6 | 4 / 4 | |
| 3.0.5 | 4 / 4 | |
| 3.0.4 | 4 / 4 | |
| 3.0.3 | 4 / 4 | |
| 3.0.2 | 4 / 4 | |
| 3.0.1 | 4 / 4 | |
| 3.0.0 | 4 / 4 | |
| 2.0.5 | 4 / 4 | |
| 2.0.4 | 4 / 4 |
v4.18.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.