@plasmicpkgs/plasmic-strapi
Plasmic Strapi 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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package from plasmicapp org; sparse metadata is consistent across all their packages. | ai | |
| dependencies | unvetted-dep:@plasmicpkgs/strapi | AI (dependencies): Same-org package from plasmicapp, same trusted publisher with 306 approved packages. | ai |
Versions (showing 69 of 69)
| Version | Deps | Published |
|---|---|---|
| 0.1.212 | 2 / 8 | |
| 0.1.211 | 2 / 8 | |
| 0.1.210 | 2 / 8 | |
| 0.1.209 | 2 / 8 | |
| 0.1.208 | 2 / 8 | |
| 0.1.207 | 2 / 8 | |
| 0.1.206 | 2 / 8 | |
| 0.1.205 | 2 / 8 | |
| 0.1.204 | 2 / 8 | |
| 0.1.203 | 2 / 8 | |
| 0.1.202 | 2 / 8 | |
| 0.1.201 | 2 / 8 | |
| 0.1.200 | 2 / 8 | |
| 0.1.199 | 2 / 8 | |
| 0.1.198 | 2 / 8 | |
| 0.1.197 | 2 / 8 | |
| 0.1.196 | 2 / 8 | |
| 0.1.195 | 2 / 8 | |
| 0.1.194 | 2 / 8 | |
| 0.1.193 | 2 / 8 | |
| 0.1.192 | 2 / 8 | |
| 0.1.191 | 2 / 8 | |
| 0.1.190 | 2 / 8 | |
| 0.1.189 | 2 / 8 | |
| 0.1.188 | 2 / 8 | |
| 0.1.187 | 2 / 8 | |
| 0.1.186 | 2 / 8 | |
| 0.1.185 | 2 / 8 | |
| 0.1.184 | 2 / 8 | |
| 0.1.183 | 2 / 8 | |
| 0.1.182 | 2 / 8 | |
| 0.1.181 | 2 / 8 | |
| 0.1.180 | 4 / 9 | |
| 0.1.179 | 4 / 9 | |
| 0.1.178 | 4 / 9 | |
| 0.1.177 | 4 / 11 | |
| 0.1.176 | 4 / 11 | |
| 0.1.175 | 4 / 11 | |
| 0.1.174 | 4 / 11 | |
| 0.1.173 | 4 / 11 | |
| 0.1.172 | 4 / 11 | |
| 0.1.171 | 4 / 11 | |
| 0.1.170 | 4 / 11 | |
| 0.1.169 | 4 / 14 | |
| 0.1.168 | 4 / 14 | |
| 0.1.167 | 4 / 14 | |
| 0.1.166 | 4 / 14 | |
| 0.1.165 | 4 / 14 | |
| 0.1.164 | 4 / 14 | |
| 0.1.163 | 4 / 14 | |
| 0.1.162 | 4 / 14 | |
| 0.1.161 | 4 / 14 | |
| 0.1.160 | 4 / 14 | |
| 0.1.159 | 4 / 14 | |
| 0.1.158 | 4 / 14 | |
| 0.1.156 | 4 / 14 | |
| 0.1.155 | 4 / 14 | |
| 0.1.154 | 4 / 14 | |
| 0.1.153 | 4 / 14 | |
| 0.1.152 | 4 / 14 | |
| 0.1.151 | 4 / 14 | |
| 0.1.150 | 4 / 14 | |
| 0.1.149 | 4 / 14 | |
| 0.1.148 | 4 / 14 | |
| 0.1.147 | 4 / 14 | |
| 0.1.146 | 4 / 14 | |
| 0.1.145 | 4 / 14 | |
| 0.1.144 | 4 / 14 | |
| 0.1.143 | 4 / 14 |
v0.1.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.211
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.166
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.165
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.163
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.158
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.156
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.155
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.154
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.153
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.151
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.145
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.