@plasmicpkgs/commerce
Plasmic registration calls for commerce components
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash.debounce | AI (phantom-deps): lodash.debounce is a declared runtime dep; phantom-dep heuristic fires due to type-only imports in devDeps. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Plasmic monorepo package; sparse README/metadata is consistent across their package family, not a spam indicator. | ai |
Versions (showing 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.0.253 | 6 / 10 | |
| 0.0.252 | 6 / 10 | |
| 0.0.251 | 6 / 10 | |
| 0.0.250 | 6 / 10 | |
| 0.0.249 | 6 / 10 | |
| 0.0.248 | 6 / 10 | |
| 0.0.247 | 6 / 10 | |
| 0.0.246 | 6 / 10 | |
| 0.0.245 | 6 / 10 | |
| 0.0.244 | 6 / 10 | |
| 0.0.243 | 6 / 10 | |
| 0.0.242 | 6 / 10 | |
| 0.0.241 | 6 / 10 | |
| 0.0.240 | 6 / 10 | |
| 0.0.239 | 6 / 10 | |
| 0.0.238 | 6 / 10 | |
| 0.0.237 | 6 / 10 | |
| 0.0.236 | 6 / 10 | |
| 0.0.235 | 7 / 9 | |
| 0.0.234 | 7 / 9 | |
| 0.0.233 | 7 / 9 | |
| 0.0.232 | 7 / 9 | |
| 0.0.231 | 7 / 9 | |
| 0.0.230 | 7 / 9 | |
| 0.0.229 | 7 / 9 | |
| 0.0.228 | 7 / 9 | |
| 0.0.227 | 7 / 9 | |
| 0.0.226 | 7 / 9 | |
| 0.0.225 | 7 / 9 | |
| 0.0.224 | 7 / 9 | |
| 0.0.223 | 7 / 11 | |
| 0.0.222 | 7 / 11 | |
| 0.0.221 | 7 / 11 | |
| 0.0.220 | 7 / 11 | |
| 0.0.219 | 7 / 11 | |
| 0.0.218 | 7 / 11 | |
| 0.0.217 | 7 / 11 | |
| 0.0.216 | 7 / 11 | |
| 0.0.215 | 7 / 11 | |
| 0.0.214 | 7 / 11 | |
| 0.0.213 | 7 / 11 | |
| 0.0.212 | 7 / 11 | |
| 0.0.211 | 7 / 11 | |
| 0.0.210 | 7 / 11 | |
| 0.0.209 | 7 / 11 | |
| 0.0.208 | 7 / 11 | |
| 0.0.207 | 7 / 11 | |
| 0.0.206 | 7 / 11 | |
| 0.0.205 | 7 / 11 | |
| 0.0.204 | 7 / 11 | |
| 0.0.203 | 7 / 11 | |
| 0.0.202 | 7 / 11 | |
| 0.0.201 | 7 / 11 | |
| 0.0.200 | 7 / 11 | |
| 0.0.199 | 7 / 11 | |
| 0.0.198 | 7 / 11 | |
| 0.0.197 | 7 / 11 | |
| 0.0.196 | 7 / 11 | |
| 0.0.195 | 7 / 11 | |
| 0.0.194 | 7 / 11 | |
| 0.0.193 | 7 / 11 |
v0.0.253
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.252
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.251
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.250
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.249
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.214
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.211
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.