@plusscommunities/pluss-maintenance-aws-a ISC 17 versions

@plusscommunities/pluss-maintenance-aws-a

npm

Extension package to enable maintenance on Pluss Communities Platform

17

Versions

ISC

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

pluss-thorpluss_pspluss_devpluss-aloys

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:https	AI (phantom-deps): Serverless AWS package; https is a Node built-in polyfill dep, not a real phantom.	ai	2026/04/29
phantom-deps	phantom-dep:twilio	AI (phantom-deps): Integration package; twilio likely used conditionally in integration modules.	ai	2026/04/29
phantom-deps	phantom-dep:aws-sdk	AI (phantom-deps): AWS Lambda package; aws-sdk commonly used via global or conditional require.	ai	2026/04/29
phantom-deps	phantom-dep:node-jose	AI (phantom-deps): Stable false positive for this package; used in auth/JWT integration code.	ai	2026/04/29
phantom-deps	phantom-dep:node-fetch	AI (phantom-deps): Stable false positive; used conditionally in integration modules.	ai	2026/04/29
phantom-deps	phantom-dep:nodemailer	AI (phantom-deps): Stable false positive; used conditionally in notification modules.	ai	2026/04/29
phantom-deps	phantom-dep:expo-server-sdk	AI (phantom-deps): Stable false positive; used conditionally for push notifications.	ai	2026/04/29
phantom-deps	phantom-dep:amazon-cognito-identity-js	AI (phantom-deps): Stable false positive; used conditionally in auth modules.	ai	2026/04/29

Versions (showing 17 of 17)

Version	Deps	Published
2.1.45	15 / 6	2026-04-15
2.1.44	15 / 6	2026-04-14
2.1.43	15 / 6	2026-04-14
2.1.42	15 / 6	2026-04-14
2.1.41	15 / 6	2026-04-14
2.1.22	15 / 6	2025-11-18
2.1.21	15 / 6	2025-11-14
2.1.20	15 / 6	2025-11-14
2.1.19	15 / 6	2025-11-14
2.1.18	15 / 6	2025-10-20
2.1.17	15 / 6	2025-09-09
2.1.16	15 / 6	2025-09-03
2.1.15	15 / 6	2025-08-21
2.1.14	15 / 6	2025-07-04
2.1.13	15 / 6	2025-06-25
2.1.12	15 / 6	2025-06-11
2.1.10	15 / 6	2025-05-14

v2.1.45

1 finding

LOW No provenance attestation provenance

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

v2.1.44

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.

v2.1.43

1 finding

LOW No provenance attestation provenance

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

v2.1.42

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.

v2.1.41

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.

v2.1.22

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pluss-thor.

LOW No provenance attestation provenance

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

v2.1.21

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.

v2.1.20

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.

v2.1.19

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.

v2.1.18

1 finding

LOW No provenance attestation provenance

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

v2.1.17

1 finding

LOW No provenance attestation provenance

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

v2.1.16

1 finding

LOW No provenance attestation provenance

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

v2.1.15

1 finding

LOW No provenance attestation provenance

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

v2.1.14

1 finding

LOW No provenance attestation provenance

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

v2.1.13

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.

v2.1.12

1 finding

LOW No provenance attestation provenance

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

v2.1.10

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.