@tuttiai/cli
Tutti CLI — scaffold and run multi-agent projects
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:joi | AI (typosquat): Scoped package @tuttiai/cli; Levenshtein match to 'joi' is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): pino is a declared logging dep; phantom-dep heuristic fires because it's used via config rather than direct import. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): pino-pretty is a declared logging formatter; same config-based usage pattern as pino. | ai | |
| phantom-deps | phantom-dep:@tuttiai/types | AI (phantom-deps): Same-org sibling package; likely used via type-only imports not caught by the heuristic. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.17.5 | 12 / 2 | |
| 0.10.0 | 11 / 2 | |
| 0.9.0 | 10 / 2 | |
| 0.8.0 | 10 / 2 | |
| 0.7.0 | 10 / 2 | |
| 0.6.0 | 10 / 2 | |
| 0.5.0 | 10 / 2 | |
| 0.4.0 | 7 / 0 | |
| 0.3.0 | 7 / 0 | |
| 0.2.0 | 7 / 0 |
v0.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.