@plasmicpkgs/react-twitter-widgets
Plasmic registration calls for react-twitter-widgets
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Plasmic monorepo sub-package; sparse metadata is a consistent pattern across all 118 approved plasmicapp packages. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.0.253 | 1 / 5 | |
| 0.0.252 | 1 / 5 | |
| 0.0.251 | 1 / 5 | |
| 0.0.250 | 1 / 5 | |
| 0.0.249 | 1 / 5 | |
| 0.0.248 | 1 / 5 | |
| 0.0.247 | 1 / 5 | |
| 0.0.246 | 1 / 5 | |
| 0.0.245 | 1 / 5 | |
| 0.0.244 | 1 / 5 | |
| 0.0.243 | 1 / 5 | |
| 0.0.239 | 1 / 5 | |
| 0.0.234 | 1 / 5 | |
| 0.0.232 | 1 / 5 | |
| 0.0.221 | 1 / 7 | |
| 0.0.220 | 1 / 7 | |
| 0.0.217 | 1 / 7 | |
| 0.0.215 | 1 / 7 | |
| 0.0.214 | 1 / 7 | |
| 0.0.213 | 1 / 7 | |
| 0.0.212 | 1 / 7 | |
| 0.0.211 | 1 / 7 | |
| 0.0.210 | 1 / 7 | |
| 0.0.209 | 1 / 7 | |
| 0.0.208 | 1 / 7 | |
| 0.0.207 | 1 / 7 | |
| 0.0.206 | 1 / 7 | |
| 0.0.205 | 1 / 7 | |
| 0.0.204 | 1 / 7 | |
| 0.0.203 | 1 / 7 | |
| 0.0.202 | 1 / 7 | |
| 0.0.201 | 1 / 7 | |
| 0.0.200 | 1 / 7 | |
| 0.0.199 | 1 / 7 | |
| 0.0.198 | 1 / 7 | |
| 0.0.197 | 1 / 7 | |
| 0.0.196 | 1 / 7 | |
| 0.0.195 | 1 / 7 | |
| 0.0.194 | 1 / 7 | |
| 0.0.193 | 1 / 7 |
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.