@stackline/load-plugin 1.0.2

@stackline/load-plugin@1.0.2

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

Source commit: e06fb12
Publication: https://github.com/alexandroit/stackline-load-plugin/actions/runs/36506660388/attempts/1
CI: https://github.com/alexandroit/stackline-load-plugin/actions/runs/36506303288

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/load-plugin 1.0.4

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

Documentation · Publication evidence

SHA-512: 11a296fbcabb637f5bee4fd73ad5fdc132ea934c6cdce22edbe2c3f6dcc1f0db1d8860c2212644f025b13993e9cd747db2f372f402a2b3901ee60a30646bc477

@stackline/load-plugin 1.0.3

Historical documentation-only publication, superseded by @stackline/load-plugin@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: 4d4a60c62f83002167df7286e599a09c4d3a697e9d70e3bfafc35ac46035cf7a6a31637646bd995dc4a6fc0d7fce7c2bafccc11827ec6ca83fa601416219e1e7

@stackline/load-plugin 1.0.0

@stackline/load-plugin@1.0.0

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

Source commit: a9b4476
Publication: https://github.com/alexandroit/stackline-load-plugin/actions/runs/36334547730/attempts/1
CI: https://github.com/alexandroit/stackline-load-plugin/actions/runs/36335126986

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.