@lynx-js/web-style-transformer

style transformer for flex、linear layout.

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

colinaaa

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Move to CI/CD (GitHub Actions) publishing, provenance unchanged/improved, not a compromise indicator.	ai	2026/07/09
bogus-package	bogus-package	AI (bogus-package): Sparse metadata typical of scoped monorepo sub-package; no malicious behavior.	ai	2026/07/09
npm-metadata	bundled-binaries	AI (npm-metadata): Expected wasm-bindgen build artifacts for this wasm transformer package.	ai	2026/07/09
publish-pattern	new-deps-added	AI (publish-pattern): wasm-feature-detect is a standard, small feature-detection lib matching the wasm build.	ai	2026/07/09

Versions (showing 20 of 20)

Version	Deps	Published
0.18.3	1 / 2	2025-11-09
0.18.2	1 / 2	2025-11-03
0.18.1	1 / 2	2025-10-25
0.18.0	1 / 2	2025-10-12
0.17.2	1 / 2	2025-10-01
0.17.1	1 / 1	2025-09-27
0.17.0	1 / 1	2025-09-21
0.16.1	1 / 1	2025-09-15
0.16.0	1 / 1	2025-09-01
0.15.7	1 / 1	2025-08-26
0.15.6	1 / 1	2025-08-15
0.15.5	1 / 1	2025-08-09
0.15.4	1 / 1	2025-08-01
0.3.3	0 / 0	2025-07-14
0.3.2	0 / 0	2025-07-11
0.3.1	0 / 0	2025-06-20
0.3.0	0 / 0	2025-04-21
0.2.3	0 / 0	2025-03-22
0.2.2	0 / 0	2025-03-09
0.2.1	0 / 0	2025-03-02

v0.18.3

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.18.2

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

HIGH Publisher changed: lynxdev-admin → GitHub Actions (on 2025-11-03) provenance

This version was published by a different npm account than previous versions on 2025-11-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.18.1

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

HIGH Publisher changed: lynxdev-admin → GitHub Actions (on 2025-10-25) provenance

This version was published by a different npm account than previous versions on 2025-10-25. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.18.0

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

HIGH Publisher changed: lynxdev-admin → GitHub Actions (on 2025-10-12) provenance

This version was published by a different npm account than previous versions on 2025-10-12. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.17.2

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

HIGH Publisher changed: lynxdev-admin → GitHub Actions (on 2025-10-01) provenance

This version was published by a different npm account than previous versions on 2025-10-01. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.17.1

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

HIGH Publisher changed: lynxdev-admin → GitHub Actions (on 2025-09-27) provenance

This version was published by a different npm account than previous versions on 2025-09-27. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.17.0

3 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

HIGH Publisher changed: lynxdev-admin → GitHub Actions (on 2025-09-21) provenance

This version was published by a different npm account than previous versions on 2025-09-21. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.1

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.0

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.15.7

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.15.6

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.15.5

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.15.4

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/legacy_bg.wasm • dist/standard_bg.wasm

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.3

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/index_bg.wasm

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.3

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.