esbuild-plugin-solid
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:babel-preset-solid | AI (dependencies): babel-preset-solid is the official SolidJS Babel preset; its use is expected and appropriate for an esbuild-solid integration plugin. | ai | |
| provenance | no-provenance | AI (provenance): Lack of provenance is common across npm and presents no direct security risk for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 3 / 8 | |
| 0.3.1 | 5 / 6 | |
| 0.3.0 | 5 / 6 | |
| 0.2.0 | 5 / 6 | |
| 0.1.0 | 5 / 6 | |
| 0.0.2 | 5 / 6 |
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.