@lwc/aria-reflection MIT 24 versions

@lwc/aria-reflection

npm Repository Homepage

ARIA element reflection polyfill for strings

24

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

lwc-admincaridyjye-sfravi.jayaramappajodaroveabdulsattarrax-it1lpomerleau

Keywords

aomarialwcpolyfillreflection

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with Salesforce/LWC monorepo CI migration pattern.	ai	2026/06/02
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy reflects monorepo release cadence, not suspicious activity; SLSA attestation confirms legitimate CI publish.	ai	2026/06/02

Versions (showing 24 of 24)

Version	Deps	Published
9.3.3	0 / 0	2026-06-01
9.2.2	0 / 0	2026-04-29
9.2.1	0 / 0	2026-04-23
9.2.0	0 / 0	2026-04-15
9.1.5	0 / 0	2026-04-28
9.1.4	0 / 0	2026-04-15
9.1.3	0 / 0	2026-04-13
9.1.2	0 / 0	2026-04-08
9.1.1	0 / 0	2026-03-25
9.1.0	0 / 0	2026-03-10
9.0.3	0 / 0	2026-03-02
9.0.2	0 / 0	2026-02-10
9.0.1	0 / 0	2026-02-05
9.0.0	0 / 0	2026-02-03
8.28.2	0 / 0	2026-01-23
8.28.1	0 / 0	2026-01-23
8.28.0	0 / 0	2026-01-13
8.27.0	0 / 0	2026-01-06
8.26.2	0 / 0	2025-12-18
8.26.1	0 / 0	2025-12-05
8.26.0	0 / 0	2025-11-19
8.25.1	0 / 0	2025-11-19
8.25.0	0 / 0	2025-11-19
8.24.0	0 / 0	2025-11-04

v9.3.3

2 findings

HIGH Publisher changed: lwc-admin → GitHub Actions (on 2026-06-01) provenance

This version was published by a different npm account than previous versions on 2026-06-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.

v9.2.2

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.

v9.2.1

1 finding

LOW No provenance attestation provenance

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

v9.2.0

1 finding

LOW No provenance attestation provenance

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

v9.1.5

1 finding

LOW No provenance attestation provenance

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

v9.1.3

1 finding

LOW No provenance attestation provenance

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

v9.1.2

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.

v9.1.1

1 finding

LOW No provenance attestation provenance

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

v9.1.0

1 finding

LOW No provenance attestation provenance

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

v9.0.3

1 finding

LOW No provenance attestation provenance

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

v9.0.2

1 finding

LOW No provenance attestation provenance

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

v9.0.1

1 finding

LOW No provenance attestation provenance

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

v9.0.0

1 finding

LOW No provenance attestation provenance

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

v8.28.2

1 finding

LOW No provenance attestation provenance

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

v8.28.1

1 finding

LOW No provenance attestation provenance

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

v8.28.0

1 finding

LOW No provenance attestation provenance

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

v8.27.0

1 finding

LOW No provenance attestation provenance

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

v8.26.2

1 finding

LOW No provenance attestation provenance

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

v8.26.1

1 finding

LOW No provenance attestation provenance

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

v8.26.0

1 finding

LOW No provenance attestation provenance

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

v8.25.1

1 finding

LOW No provenance attestation provenance

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

v8.25.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.

v8.24.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.