@hpcc-js/esbuild-plugins
Various esbuild plugins
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established hpcc-systems org package; lack of provenance is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:esbuild-plugin-inline-css | AI (phantom-deps): Declared dep used in config/plugin wiring, not directly imported in source; stable false positive for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.9.6 | 7 / 3 | |
| 1.9.5 | 7 / 3 | |
| 1.9.4 | 8 / 3 | |
| 1.9.3 | 8 / 3 | |
| 1.9.2 | 8 / 2 | |
| 1.9.1 | 8 / 2 | |
| 1.9.0 | 8 / 2 | |
| 1.8.11 | 8 / 2 | |
| 1.8.10 | 8 / 2 | |
| 1.8.9 | 8 / 2 | |
| 1.8.8 | 8 / 2 | |
| 1.8.7 | 8 / 2 | |
| 1.8.5 | 7 / 2 | |
| 1.4.4 | 10 / 0 | |
| 1.4.1 | 7 / 0 | |
| 1.4.0 | 7 / 0 | |
| 1.3.1 | 3 / 0 | |
| 1.3.0 | 7 / 0 | |
| 1.2.0 | 3 / 0 | |
| 1.1.2 | 3 / 0 | |
| 1.1.1 | 4 / 0 | |
| 1.1.0 | 4 / 0 | |
| 1.0.10 | 4 / 0 | |
| 1.0.9 | 4 / 0 | |
| 1.0.8 | 4 / 0 | |
| 1.0.7 | 4 / 0 | |
| 1.0.6 | 2 / 2 | |
| 1.0.5 | 4 / 0 | |
| 1.0.4 | 2 / 2 | |
| 1.0.3 | 4 / 0 | |
| 1.0.2 | 4 / 0 | |
| 1.0.1 | 4 / 0 |
v1.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.