@ezs/conditor
ezs statements for Conditor
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:csv-string | AI (dependencies): csv-string is a well-known CSV parsing utility; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:stream-write | AI (dependencies): stream-write is a small, benign stream utility; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:fetch-with-proxy | AI (dependencies): fetch-with-proxy is a standard HTTP fetch wrapper; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:node-abort-controller | AI (dependencies): node-abort-controller is a well-known AbortController polyfill; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.14.1 | 14 / 0 | |
| 2.14.0 | 14 / 0 | |
| 2.13.8 | 14 / 0 | |
| 2.13.7 | 14 / 0 |
v2.14.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (touv) than the most recent previously approved version (parmentf) on 2026-06-04, but touv is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (parmentf) than the most recent previously approved version (touv) on 2026-05-18, but parmentf is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.