@plasmicpkgs/commerce-commercetools
Plasmic registration calls for commercetools commerce provider
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped Plasmic monorepo integration package; sparse README/metadata is normal for this publisher's pattern. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only peer dep; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@commercetools/ts-sdk-apm | AI (phantom-deps): APM SDK may be loaded conditionally; stable false positive for this integration package. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): qs is a declared runtime dependency in package.json; phantom-dep is a false positive for this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.0.195 | 6 / 9 | |
| 0.0.194 | 6 / 9 | |
| 0.0.193 | 6 / 9 | |
| 0.0.192 | 6 / 9 | |
| 0.0.191 | 6 / 9 | |
| 0.0.190 | 6 / 9 | |
| 0.0.189 | 6 / 9 | |
| 0.0.188 | 6 / 9 | |
| 0.0.187 | 6 / 9 | |
| 0.0.186 | 6 / 9 | |
| 0.0.185 | 7 / 8 | |
| 0.0.184 | 7 / 8 | |
| 0.0.183 | 7 / 8 | |
| 0.0.182 | 7 / 8 | |
| 0.0.181 | 7 / 8 | |
| 0.0.180 | 7 / 8 | |
| 0.0.179 | 7 / 8 | |
| 0.0.178 | 7 / 8 | |
| 0.0.177 | 7 / 8 | |
| 0.0.176 | 7 / 8 | |
| 0.0.175 | 7 / 8 | |
| 0.0.174 | 7 / 8 | |
| 0.0.173 | 7 / 10 | |
| 0.0.172 | 7 / 10 | |
| 0.0.171 | 7 / 10 | |
| 0.0.168 | 8 / 10 | |
| 0.0.167 | 8 / 10 | |
| 0.0.166 | 8 / 10 | |
| 0.0.164 | 8 / 10 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.184
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.182
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.180
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.172
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.171
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.168
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.