@plasmicapp/cli No license 43 versions

@plasmicapp/cli

npm

plasmic cli for syncing local code with Plasmic designs

43

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

plasmicapp

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@plasmicapp/react-web	AI (phantom-deps): Same-org sibling package, expected dependency.	ai	2026/07/22
phantom-deps	phantom-dep:chalk	AI (phantom-deps): chalk is a standard CLI color dep, likely used indirectly; stable false positive.	ai	2026/07/22
phantom-deps	phantom-dep:@types/socket.io-client	AI (phantom-deps): Types-only package, not expected to be directly imported.	ai	2026/07/22
dependencies	unvetted-dep:@plasmicapp/code-merger	AI (dependencies): First-party sibling package from same publisher/org.	ai	2026/07/22
phantom-deps	phantom-dep:fast-glob	AI (phantom-deps): Likely used via dynamic/glob resolution; stable FP for this CLI package.	ai	2026/07/22
phantom-deps	phantom-dep:latest-version	AI (phantom-deps): Update-notifier related dep, plausibly used indirectly; stable FP.	ai	2026/07/22
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped package @plasmicapp/cli; Levenshtein match to 'joi' is a false positive with no brand impersonation.	ai	2026/04/29
semgrep	semgrep:dynamic-require	AI (semgrep): Loads user's next.config.js to detect Next.js version; standard CLI config detection pattern.	ai	2026/04/29
semgrep	semgrep:base64-decode	AI (semgrep): Decodes image asset blobs to write to disk; legitimate CLI export functionality.	ai	2026/04/29

Versions (showing 43 of 143)

Version	Deps	Published
0.1.209	29 / 26	2023-02-08
0.1.208	29 / 26	2023-02-04
0.1.206	29 / 26	2023-02-02
0.1.205	29 / 26	2023-01-26
0.1.204	29 / 26	2023-01-25
0.1.203	29 / 26	2023-01-25
0.1.202	29 / 26	2023-01-24
0.1.201	29 / 26	2023-01-23
0.1.200	29 / 26	2023-01-21
0.1.199	29 / 26	2023-01-20
0.1.198	29 / 26	2023-01-20
0.1.197	29 / 26	2023-01-19
0.1.196	29 / 26	2023-01-18
0.1.195	29 / 26	2023-01-18
0.1.194	29 / 26	2023-01-14
0.1.193	29 / 26	2023-01-13
0.1.192	29 / 26	2023-01-11
0.1.186	31 / 26	2022-08-15
0.1.182	31 / 26	2022-06-10
0.1.180	31 / 26	2022-06-07
0.1.176	31 / 26	2022-03-28
0.1.166	31 / 26	2021-10-26
0.1.165	31 / 26	2021-10-26
0.1.158	29 / 26	2021-07-30
0.1.157	29 / 26	2021-06-22
0.1.156	29 / 26	2021-06-21
0.1.155	29 / 26	2021-06-21
0.1.67	24 / 25	2020-11-07
0.1.65	24 / 25	2020-10-27
0.1.57	30 / 21	2020-09-02
0.1.5	14 / 11	2020-05-22
0.1.4	14 / 11	2020-05-20
0.1.3	14 / 11	2020-05-14
0.1.2	14 / 11	2020-05-07
0.1.1	14 / 11	2020-05-04
0.1.0	14 / 11	2020-05-01
0.0.9	14 / 11	2020-05-01
0.0.8	14 / 11	2020-04-30
0.0.7	12 / 11	2020-04-28
0.0.5	12 / 11	2020-04-27
0.0.4	9 / 9	2020-04-18
0.0.3	9 / 9	2020-04-12
0.0.2	9 / 9	2020-04-11

v0.1.209

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.208

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.206

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.205

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.204

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.203

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.202

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.201

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.200

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.199

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.198

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.197

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.196

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.195

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.194

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.193

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.192

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.186

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.182

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.180

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.176

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.166

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.165

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.158

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.157

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.156

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.155

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.67

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.65

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.57

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.