@stackline/uglify-js 1.0.2

@stackline/uglify-js@1.0.2

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

Source commit: 6c528d1
Publication: https://github.com/alexandroit/stackline-uglify-js/actions/runs/36506227617/attempts/1
CI: https://github.com/alexandroit/stackline-uglify-js/actions/runs/36506063451

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/uglify-js 1.0.5

Documentation and package discovery update for @stackline/uglify-js@1.0.5.

Uses the published 1.0.2 tarball as the baseline. Only the README and package documentation/discovery metadata changed. All other 23 file contents are identical; runtime/development dependencies, original authors and license are preserved.

Documentation · Publication evidence

SHA-512: 831f74b61e3330adbb1f5a5d7b62fe636992bd27c546c22360f07461aa46283357f678bc5174339f634c13681bf564cc67ed3e8f0f25214c77e5b3c04ba656a4

@stackline/uglify-js 1.0.4

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

Original GitHub Actions publication

SHA-512: d40e365b3a10bd0f20fbbcc6a87f56008052b64b93ae8649edf6864464bd86e00d26c75c700d5cbe2194f7e3232454b92a27072476821e1bbae0a074bdb1fc1b

@stackline/uglify-js 1.0.0

@stackline/uglify-js@1.0.0

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

Source commit: c55d119
Publication: https://github.com/alexandroit/stackline-uglify-js/actions/runs/36334956912/attempts/1
CI: https://github.com/alexandroit/stackline-uglify-js/actions/runs/36335135263

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.