@eik/esbuild-plugin
esbuild plugin for loading import maps from a Eik server and applying the mapping to ECMAScript modules in preparation for upload to the same server.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Published with SLSA provenance via CI; no code changes; consistent with org maintainer onboarding. | ai | |
| dependencies | unvetted-dep:esbuild-plugin-import-map | AI (dependencies): Core runtime dep matching package purpose; pinned version, no malware signals, stable across versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.15 | 2 / 15 | |
| 2.0.13 | 2 / 15 | |
| 2.0.10 | 2 / 15 | |
| 2.0.9 | 2 / 15 | |
| 2.0.8 | 2 / 15 | |
| 2.0.6 | 2 / 15 | |
| 2.0.0 | 2 / 14 |
v2.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.