Skip to content

Releases

@stackline/crc-32 1.0.3

Choose a tag to compare

@github-actions github-actions released this 04 Nov 19:54
Immutable release. Only release title and notes can be modified.

@stackline/crc-32@1.0.3

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

Source commit: ddc2ce5
Publication: https://github.com/alexandroit/stackline-crc-32/actions/runs/41899170057/attempts/1
CI: https://github.com/alexandroit/stackline-crc-32/actions/runs/41879752064

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/crc-32 1.0.2

Choose a tag to compare

@github-actions github-actions released this 29 Sep 02:57
Immutable release. Only release title and notes can be modified.

Documentation and package discovery update for @stackline/crc-32@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 7 file contents are identical; runtime/development dependencies, original authors and license are preserved.

Documentation · Publication evidence

SHA-512: 19f4ddd100b0beb7d8adcb59528bc13c076c0a361333b468f885f7edd377c9beaf43eebdc0915f4902318e7f8ad20cc7b8ba34895c63b67c3d47de0c46ced445

@stackline/crc-32 1.0.0

Choose a tag to compare

@github-actions github-actions released this 27 Sep 17:01
Immutable release. Only release title and notes can be modified.

@stackline/crc-32@1.0.0

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

Source commit: a3b5eb2
Publication: https://github.com/alexandroit/stackline-crc-32/actions/runs/36334927635/attempts/1
CI: https://github.com/alexandroit/stackline-crc-32/actions/runs/36335129191

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.