@salesforce/lds-adapters-industries-explainability SEE LICENSE IN LICENSE.txt 51 versions

@salesforce/lds-adapters-industries-explainability

npm

API to fetch and post centralised explainability related meta data and transactional data

51

Versions

SEE LICENSE IN LICENSE.txt

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ire-npm-team-userjimjagsalesforce-releasesjasonschroeder-sfdcmobifylwc-adminsalesforce-admin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): lwc-admin is a well-established Salesforce org publisher with 1699 approved packages; transition from individual accounts is expected.	ai	2026/05/07
maintainer-change	maintainer-added	AI (maintainer-change): salesforce-admin addition aligns with Salesforce org-level account consolidation pattern seen across this publisher.	ai	2026/05/07
maintainer-change	maintainer-removed	AI (maintainer-change): Mass removal of individual Salesforce employee accounts consistent with org-level consolidation to lwc-admin/salesforce-admin.	ai	2026/05/07
phantom-deps	phantom-dep:@salesforce/lds-bindings	AI (phantom-deps): Same org scope; lds-bindings is a declared runtime dep used by the built dist artifacts, not directly imported in source.	ai	2026/05/07

Versions (showing 51 of 93)

View all versions

Version	Deps	Published
1.442.0	1 / 2	2026-06-08
1.441.0	1 / 2	2026-06-03
1.440.0	1 / 2	2026-05-28
1.439.0	1 / 2	2026-05-28
1.438.1	1 / 2	2026-05-28
1.438.0	1 / 2	2026-05-27
1.437.0	1 / 2	2026-05-20
1.436.0	1 / 2	2026-05-13
1.435.1	1 / 2	2026-05-08
1.435.0	1 / 2	2026-05-07
1.434.0	1 / 2	2026-04-29
1.433.0	1 / 2	2026-04-22
1.432.0	1 / 2	2026-04-16
1.431.0	1 / 2	2026-04-15
1.430.0	1 / 2	2026-04-11
1.429.0	1 / 2	2026-04-08
1.428.0	1 / 2	2026-04-01
1.427.0	1 / 2	2026-03-25
1.426.1	1 / 2	2026-03-18
1.425.0	1 / 2	2026-03-12
1.424.0	1 / 2	2026-03-11
1.423.0	1 / 2	2026-03-04
1.422.0	1 / 2	2026-03-04
1.421.1	1 / 2	2026-02-26
1.421.0	1 / 2	2026-02-25
1.420.0	1 / 2	2026-02-18
1.419.0	1 / 2	2026-02-13
1.418.0	1 / 2	2026-02-13
1.417.0	1 / 2	2026-02-11
1.416.1	1 / 2	2026-02-04
1.416.0	1 / 2	2026-02-04
1.415.0	1 / 2	2026-01-28
1.414.1	1 / 2	2026-01-22
1.414.0	1 / 2	2026-01-22
1.413.0	1 / 2	2026-01-14
1.412.1	1 / 2	2026-01-08
1.412.0	1 / 2	2026-01-07
1.411.0	1 / 2	2025-12-26
1.410.1	1 / 2	2025-12-19
1.410.0	1 / 2	2025-12-18
1.409.0	1 / 2	2025-12-15
1.405.0	1 / 2	2025-12-03
1.404.0	1 / 2	2025-11-25
1.403.0	1 / 2	2025-11-24
1.402.0	1 / 2	2025-11-19
1.401.0	1 / 2	2025-11-12
1.400.0	1 / 2	2025-11-05
1.399.0	1 / 2	2025-11-03
1.398.0	1 / 2	2025-10-30
1.397.0	1 / 2	2025-10-29
1.396.0	1 / 2	2025-10-22

v1.442.0

1 finding

LOW No provenance attestation provenance

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

v1.441.0

1 finding

LOW No provenance attestation provenance

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

v1.440.0

1 finding

LOW No provenance attestation provenance

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

v1.439.0

1 finding

LOW No provenance attestation provenance

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

v1.438.1

1 finding

LOW No provenance attestation provenance

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

v1.438.0

1 finding

LOW No provenance attestation provenance

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

v1.437.0

1 finding

LOW No provenance attestation provenance

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

v1.436.0

1 finding

LOW No provenance attestation provenance

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

v1.435.1

1 finding

LOW No provenance attestation provenance

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

v1.435.0

1 finding

LOW No provenance attestation provenance

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

v1.434.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.

v1.433.0

1 finding

LOW No provenance attestation provenance

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

v1.432.0

1 finding

LOW No provenance attestation provenance

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

v1.431.0

1 finding

LOW No provenance attestation provenance

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

v1.430.0

1 finding

LOW No provenance attestation provenance

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

v1.429.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.

v1.428.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.

v1.427.0

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-03-25) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-03-18) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-03-12) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-03-11) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-03-04) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-03-04) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-02-26) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-02-25) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-02-18) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-02-13) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-02-13) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-02-11) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-02-04) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-02-04) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-01-28) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-01-22) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-01-22) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-01-14) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-01-08) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2026-01-07) provenance

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

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2025-12-26) provenance

This version was published by a different npm account than previous versions on 2025-12-26. 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.410.1

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2025-12-19) provenance

This version was published by a different npm account than previous versions on 2025-12-19. 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.410.0

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2025-12-18) provenance

This version was published by a different npm account than previous versions on 2025-12-18. 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.409.0

2 findings

HIGH Publisher changed: dme722 → lwc-admin (on 2025-12-15) provenance

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

1 finding

LOW No provenance attestation provenance

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

v1.404.0

1 finding

LOW No provenance attestation provenance

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

v1.403.0

1 finding

LOW No provenance attestation provenance

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

v1.402.0

1 finding

LOW No provenance attestation provenance

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

v1.401.0

1 finding

LOW No provenance attestation provenance

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

v1.400.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.

v1.399.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.

v1.398.0

1 finding

LOW No provenance attestation provenance

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

v1.397.0

1 finding

LOW No provenance attestation provenance

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

v1.396.0

1 finding

LOW No provenance attestation provenance

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