@effectstream/ord
Ord binary wrapper for EffectStream
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Binary wrapper passes process.env to child process — standard pattern, not exfiltration. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @effectstream/ord; not a typosquat of cors — different namespace and purpose. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @effectstream/ord; not a typosquat of zod — different namespace and purpose. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.100.18 | 1 / 0 | |
| 0.100.17 | 1 / 0 | |
| 0.100.16 | 1 / 0 | |
| 0.100.15 | 1 / 0 | |
| 0.100.14 | 1 / 0 | |
| 0.100.13 | 1 / 0 | |
| 0.100.12 | 1 / 0 | |
| 0.100.11 | 1 / 0 | |
| 0.100.10 | 1 / 0 | |
| 0.100.9 | 1 / 0 | |
| 0.100.8 | 1 / 0 |
v0.100.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.10
2 findingsSpreading entire process.env into an object — may capture all secrets 158 | // Set environment variables for ord CLI commands 159 | // Note: ord also supports ORD_SERVER_URL environment variable, but --server-url flag is preferred > 160 | const env = { ...process.env }; 161 | 162 | return new Promise((resolve, reject) => {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.100.9
2 findingsSpreading entire process.env into an object — may capture all secrets 158 | // Set environment variables for ord CLI commands 159 | // Note: ord also supports ORD_SERVER_URL environment variable, but --server-url flag is preferred > 160 | const env = { ...process.env }; 161 | 162 | return new Promise((resolve, reject) => {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.100.8
2 findingsSpreading entire process.env into an object — may capture all secrets 158 | // Set environment variables for ord CLI commands 159 | // Note: ord also supports ORD_SERVER_URL environment variable, but --server-url flag is preferred > 160 | const env = { ...process.env }; 161 | 162 | return new Promise((resolve, reject) => {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.