@stackline/cfb 1.0.2

@stackline/cfb@1.0.2

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

Source commit: 0e3893f
Publication: https://github.com/alexandroit/stackline-cfb/actions/runs/36507602458/attempts/1
CI: https://github.com/alexandroit/stackline-cfb/actions/runs/36507366596

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/cfb 1.0.4

Documentation and package discovery update for @stackline/cfb@1.0.4.

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

Documentation · Publication evidence

SHA-512: 90ae6c97f22c1194387e25f89ecb51069fefda9ed0e6011dca0eb4f044425e871e9238270a49a4c98152a21819e6c54c7afe9f945e2bec26ad582e36efad769b

@stackline/cfb 1.0.3

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

Original GitHub Actions publication

SHA-512: 7ef1e5f54cfacc3aee8cee5462a84382602d2f1748390fbc8744f53c708b804af26f1c219b3a144267a31dceaa0c0d1ccace526352c3384b3274f5e57ba2967c

@stackline/cfb 1.0.0

@stackline/cfb@1.0.0

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

Source commit: 1739408
Publication: https://github.com/alexandroit/stackline-cfb/actions/runs/36334951149/attempts/1
CI: https://github.com/alexandroit/stackline-cfb/actions/runs/36335130576

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.