@plasmicapp/cli
plasmic cli for syncing local code with Plasmic designs
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
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 @plasmicapp/cli; Levenshtein match to 'joi' is a false positive with no brand impersonation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes image asset blobs to write to disk; legitimate CLI export functionality. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user's next.config.js to detect Next.js version; standard CLI config detection pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.364 | 0 / 57 | |
| 0.1.363 | 0 / 57 | |
| 0.1.362 | 0 / 57 | |
| 0.1.361 | 0 / 57 | |
| 0.1.360 | 0 / 57 |
v0.1.364
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.363
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.362
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.361
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.360
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.