@lit/reactive-element BSD-3-Clause 31 versions

@lit/reactive-element

npm Repository Homepage

A simple low level base class for creating fast, lightweight web components

31

Versions

BSD-3-Clause

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

kevinpschaafsorvellricticgraynortonjustinfagnaniaomarkslit-robotaugustjk

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition from justinfagnani to lit-robot is a known, legitimate move to CI-based publishing for the Lit project.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): lit-robot is the official Lit project bot account with a strong track record (38 approved, 0 rejected).	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in 2022 before Sigstore provenance was standard; informational only.	ai	2026/04/24
source-diff	obfuscated-file:node/reactive-element.js	AI (source-diff): Standard rollup-minified output for Node.js export condition; source maps included. Lit's documented build pipeline.	ai	2026/04/24

Versions (showing 31 of 31)

Version	Deps	Published
2.1.2	1 / 11	2025-12-23
2.1.1	1 / 11	2025-07-11
2.1.0	1 / 11	2025-04-11
2.0.4	1 / 10	2024-01-31
2.0.3	1 / 10	2024-01-09
2.0.2	1 / 10	2023-11-16
2.0.1	1 / 10	2023-10-28
2.0.0	1 / 10	2023-10-10
1.6.3	1 / 9	2023-08-02
1.6.2	1 / 9	2023-06-01
1.6.1	1 / 9	2023-01-12
1.6.0	1 / 9	2023-01-09
1.5.0	0 / 9	2022-12-08
1.4.2	0 / 9	2022-11-03
1.4.1	0 / 9	2022-08-18
1.4.0	0 / 9	2022-08-12
1.3.4	0 / 9	2022-07-22
1.3.3	0 / 16	2022-06-29
1.3.2	0 / 16	2022-04-29
1.3.1	0 / 16	2022-03-15
1.3.0	0 / 16	2022-02-18
1.2.3	0 / 16	2022-02-15
1.2.2	0 / 16	2022-02-07
1.2.1	0 / 16	2022-01-25
1.2.0	0 / 16	2022-01-13
1.1.2	0 / 16	2022-01-12
1.1.1	0 / 16	2022-01-06
1.1.0	0 / 16	2022-01-05
1.0.2	0 / 16	2021-11-09
1.0.1	0 / 16	2021-10-07
1.0.0	0 / 16	2021-09-21

v2.1.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.

v2.1.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.

v2.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

2 findings

HIGH New obfuscated file: node/reactive-element.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.2

2 findings

HIGH New obfuscated file: node/reactive-element.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

2 findings

HIGH New obfuscated file: node/reactive-element.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

2 findings

HIGH New obfuscated file: node/reactive-element.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

2 findings

HIGH Publisher changed: justinfagnani → lit-robot (on 2022-03-15) provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

2 findings

HIGH Publisher changed: kevinpschaaf → justinfagnani (on 2021-10-07) provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

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.