@pob/rollup-esbuild
rollup configuration with typescript for pob
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@rollup/plugin-run | AI (dependencies): Official @rollup org plugin; stable dependency in this build-tool package. | ai | |
| dependencies | unvetted-dep:rollup-config-external-dependencies | AI (dependencies): Known rollup ecosystem utility; consistent dependency across versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with consistent authorship; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): esbuild is listed as a direct dependency in package.json and used as a runtime binary; phantom-dep false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 9.0.0 | 8 / 0 | |
| 8.3.0 | 8 / 0 | |
| 8.2.0 | 8 / 0 | |
| 8.1.2 | 8 / 0 | |
| 8.1.1 | 8 / 0 | |
| 8.1.0 | 8 / 0 | |
| 8.0.0 | 8 / 0 | |
| 7.4.1 | 8 / 0 | |
| 7.4.0 | 8 / 0 |
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.