@stackline/exit-on-epipe 1.0.3

@stackline/exit-on-epipe@1.0.3

Independent Stackline maintenance fork. Original authors and licenses are retained.

Source commit: c950f9f
Publication: https://github.com/alexandroit/stackline-exit-on-epipe/actions/runs/41887324392/attempts/1
CI: https://github.com/alexandroit/stackline-exit-on-epipe/actions/runs/41879694218

The published tarball is the exact artifact tested in CI. Registry bytes, provenance,
signatures, direct and aliased installs, and zero known production audit findings were verified.
Audit results are a point-in-time check, not a guarantee of absolute security.

See the repository changelog and notices for the focused fixes and upstream attribution.

@stackline/exit-on-epipe 1.0.2

Documentation and package discovery update for @stackline/exit-on-epipe@1.0.2.

Uses the published 1.0.0 tarball as the baseline. Only the README and package version, keywords and homepage changed. All other 4 file contents are identical; runtime/development dependencies, original authors and license are preserved.

Documentation · Publication evidence

SHA-512: 6dd79f1b3669e9f8359f2a07f29019a6cce4d20fa9d94771ae306808af24cb0899aa7d237f648795521f3ff1033733c9a429a614da440f16a6071206c32439f7

@stackline/exit-on-epipe 1.0.1

Historical documentation-only publication, superseded by @stackline/exit-on-epipe@1.0.2. Runtime files and dependency requirements are unchanged from 1.0.0. Original authors and licenses remain preserved.

Original GitHub Actions publication

SHA-512: 578e4a323ebeb486e4d340799ca7a059ac1820581f8ad53c00d6d836a81ecace0303dc1ee144f160a3404a7f9a5c61dedb381854609230c3c2f51d18bbc5e897

@stackline/exit-on-epipe 1.0.0

@stackline/exit-on-epipe@1.0.0

Independent Stackline maintenance fork. Original authors and licenses are retained.

Source commit: 390cd0d
Publication: https://github.com/alexandroit/stackline-exit-on-epipe/actions/runs/36334488476/attempts/1
CI: https://github.com/alexandroit/stackline-exit-on-epipe/actions/runs/36335126013

The published tarball is the exact artifact tested in CI. Registry bytes, provenance,
signatures, direct and aliased installs, and zero known production audit findings were verified.
Audit results are a point-in-time check, not a guarantee of absolute security.

See the repository changelog and notices for the focused fixes and upstream attribution.