@plusscommunities/pluss-core-web ISC 51 versions

@plusscommunities/pluss-core-web

npm

Core extension package for Pluss Communities platform

51

Versions

ISC

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

pluss-thorpluss_pspluss_devpluss-aloys

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	large-new-source-files	AI (source-diff): Consistent with adding a new UI feature module, no malicious indicators.	ai	2026/07/23
provenance	publisher-changed-stale	AI (provenance): Stale publisher change, 1778d live on npm, trusted publisher track record.	ai	2026/07/23
maintainer-change	maintainer-added	AI (maintainer-change): Same long-standing publisher, consistent with legitimate account continuity.	ai	2026/07/23
publish-pattern	new-deps-added	AI (publish-pattern): jquery/react-dropzone are common, legitimate front-end deps fitting package purpose.	ai	2026/07/23
semgrep	semgrep:base64-decode	AI (semgrep): Decodes canvas image data URL (strips data:image prefix); not a payload-hiding pattern.	ai	2026/04/29

Versions (showing 51 of 80)

View all versions

Version	Deps	Published
1.6.18	1 / 11	2026-03-03
1.6.17	1 / 11	2026-02-19
1.6.16	1 / 11	2026-02-19
1.6.14	1 / 11	2026-02-04
1.6.13	1 / 11	2025-12-16
1.6.9	1 / 11	2025-11-17
1.6.8	1 / 11	2025-10-17
1.6.7	1 / 11	2025-10-17
1.6.6	1 / 11	2025-06-12
1.6.5	1 / 11	2025-03-14
1.6.2	1 / 11	2025-02-14
1.5.1	1 / 11	2024-12-05
1.5.0	1 / 11	2024-11-20
1.4.37	1 / 11	2024-11-20
1.4.36	14 / 11	2024-11-18
1.4.35	14 / 11	2024-11-18
1.4.34	14 / 11	2024-10-23
1.4.33	14 / 11	2024-09-25
1.4.32	14 / 11	2024-09-25
1.4.31	14 / 11	2024-01-30
1.4.30	14 / 11	2023-11-20
1.4.29	14 / 11	2023-11-15
1.4.28	14 / 11	2023-11-15
1.4.27	14 / 11	2023-10-05
1.4.26	14 / 11	2023-08-31
1.4.25	14 / 11	2023-08-25
1.4.24	14 / 11	2023-07-14
1.4.23	14 / 11	2023-06-20
1.4.22	14 / 11	2023-05-30
1.4.21	14 / 11	2023-05-26
1.4.20	11 / 11	2023-05-24
1.4.19	11 / 11	2023-05-19
1.4.18	11 / 11	2023-05-12
1.4.17	11 / 11	2023-03-08
1.4.12	11 / 11	2022-09-29
1.4.11	11 / 11	2022-08-31
1.4.10	11 / 11	2022-08-31
1.4.9	11 / 11	2022-07-20
1.4.5	11 / 11	2022-06-03
1.4.4	11 / 11	2022-05-17
1.4.3	11 / 11	2022-05-16
1.4.2	11 / 11	2022-05-10
1.4.1	11 / 11	2022-04-13
1.4.0	11 / 11	2022-04-06
1.3.1	11 / 11	2022-03-04
1.2.11	10 / 11	2022-01-14
1.2.10	10 / 11	2022-01-06
1.2.9	10 / 11	2021-12-14
1.2.8	10 / 11	2021-12-08
1.2.7	10 / 11	2021-12-08
1.2.6	10 / 11	2021-12-08

v1.6.5

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.5.1

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

1 finding

LOW No provenance attestation provenance

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

v1.4.37

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.4.36

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.4.35

1 finding

LOW No provenance attestation provenance

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

v1.4.34

1 finding

LOW No provenance attestation provenance

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

v1.4.33

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.4.32

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.4.31

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2024-01-30, unremoved on npm for 904d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2024-01-30. It has since remained available on npm for 904 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.30

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-11-20, unremoved on npm for 975d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-11-20. It has since remained available on npm for 975 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.29

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-11-15, unremoved on npm for 980d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-11-15. It has since remained available on npm for 980 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.28

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-11-15, unremoved on npm for 980d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-11-15. It has since remained available on npm for 980 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.27

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-10-05, unremoved on npm for 1021d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-10-05. It has since remained available on npm for 1021 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.26

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-08-31, unremoved on npm for 1057d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-08-31. It has since remained available on npm for 1057 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.25

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-08-25, unremoved on npm for 1062d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-08-25. It has since remained available on npm for 1062 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.24

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-07-14, unremoved on npm for 1104d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-07-14. It has since remained available on npm for 1104 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.23

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-06-20, unremoved on npm for 1128d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-06-20. It has since remained available on npm for 1128 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.22

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-05-30, unremoved on npm for 1149d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-05-30. It has since remained available on npm for 1149 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.21

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-05-26, unremoved on npm for 1153d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-05-26. It has since remained available on npm for 1153 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.20

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-05-24, unremoved on npm for 1156d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-05-24. It has since remained available on npm for 1156 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.19

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-05-19, unremoved on npm for 1160d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-05-19. It has since remained available on npm for 1160 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.18

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-05-12, unremoved on npm for 1167d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-05-12. It has since remained available on npm for 1167 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.17

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2023-03-08, unremoved on npm for 1232d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2023-03-08. It has since remained available on npm for 1232 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.12

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2022-09-29, unremoved on npm for 1392d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2022-09-29. It has since remained available on npm for 1392 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.11

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2022-08-31, unremoved on npm for 1421d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2022-08-31. It has since remained available on npm for 1421 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.10

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2022-08-31, unremoved on npm for 1421d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2022-08-31. It has since remained available on npm for 1421 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.9

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2022-07-20, unremoved on npm for 1463d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2022-07-20. It has since remained available on npm for 1463 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.5

1 finding

LOW No provenance attestation provenance

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

v1.4.4

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2022-05-17, unremoved on npm for 1528d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2022-05-17. It has since remained available on npm for 1528 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.3

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2022-05-16, unremoved on npm for 1528d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2022-05-16. It has since remained available on npm for 1528 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2022-05-10, unremoved on npm for 1534d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2022-05-10. It has since remained available on npm for 1534 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

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

1 finding

LOW No provenance attestation provenance

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

v1.2.11

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2022-01-14, unremoved on npm for 1650d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2022-01-14. It has since remained available on npm for 1650 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.2.10

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2022-01-06, unremoved on npm for 1658d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2022-01-06. It has since remained available on npm for 1658 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.2.9

2 findings

MEDIUM Publisher changed: pluss_ps → pluss-thor (on 2021-12-14, unremoved on npm for 1681d) provenance

This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss_ps) on 2021-12-14. It has since remained available on npm for 1681 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.2.8

1 finding

LOW No provenance attestation provenance

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

v1.2.7

1 finding

LOW No provenance attestation provenance

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

v1.2.6

1 finding

LOW No provenance attestation provenance

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