@getpara/cli
Unified CLI for Para SDK - project scaffolding, diagnostics, and API key management
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@getpara/shared | AI (phantom-deps): Same org scope; bundled into dist, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Bundled ESM CLI via esbuild; deps not directly imported in source but used at build time. | ai | |
| phantom-deps | phantom-dep:ignore | AI (phantom-deps): Same bundled CLI pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Same bundled CLI pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Same bundled CLI pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): CLI tool that uses typescript for user project type-checking; bundled pattern. | ai | |
| phantom-deps | phantom-dep:@clack/prompts | AI (phantom-deps): Same bundled CLI pattern; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @getpara package; Levenshtein match to 'joi' is coincidental, not a typosquat. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 8 / 3 | |
| 3.0.0 | 8 / 3 | |
| 2.32.1 | 7 / 4 | |
| 2.32.0 | 7 / 4 | |
| 2.31.0 | 7 / 4 | |
| 2.30.0 | 7 / 4 | |
| 2.29.0 | 7 / 4 | |
| 2.28.0 | 7 / 4 | |
| 2.27.0 | 7 / 4 | |
| 2.26.0 | 7 / 4 | |
| 2.25.0 | 7 / 4 | |
| 2.24.0 | 7 / 4 | |
| 2.23.0 | 7 / 4 | |
| 2.22.0 | 7 / 4 | |
| 2.21.0 | 7 / 4 | |
| 2.20.0 | 7 / 4 | |
| 2.19.0 | 7 / 4 | |
| 2.18.1 | 7 / 4 | |
| 2.18.0 | 7 / 4 | |
| 2.17.0 | 7 / 4 | |
| 2.16.0 | 7 / 4 | |
| 2.15.1 | 7 / 4 | |
| 2.15.0 | 7 / 4 |
v3.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nsquare) than the most recent previously approved version (tbosch) on 2026-06-05, but nsquare is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tbosch) than the most recent previously approved version (nsquare) on 2026-05-28, but tbosch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.