@plusscommunities/pluss-maintenance-aws-enquiry ISC 21 versions

@plusscommunities/pluss-maintenance-aws-enquiry

npm

Extension package to enable maintenance on Pluss Communities Platform

21

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
provenance	missing-githead	AI (provenance): Established publisher with clean track record; likely a CI/CD environment change rather than a supply chain concern.	ai	2026/05/03
phantom-deps	phantom-dep:twilio	AI (phantom-deps): Integration dependency used conditionally; phantom-dep heuristic fires on config references.	ai	2026/04/29
phantom-deps	phantom-dep:aws-sdk	AI (phantom-deps): AWS SDK used via SDK-level calls, not direct import; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:node-jose	AI (phantom-deps): Conditional integration dep; phantom-dep heuristic fires on config references.	ai	2026/04/29
phantom-deps	phantom-dep:https	AI (phantom-deps): Serverless AWS package; https is a Node built-in polyfill dep, not a real import concern.	ai	2026/04/29
phantom-deps	phantom-dep:nodemailer	AI (phantom-deps): Conditional integration dep; phantom-dep heuristic fires on config references.	ai	2026/04/29
phantom-deps	phantom-dep:expo-server-sdk	AI (phantom-deps): Conditional integration dep; phantom-dep heuristic fires on config references.	ai	2026/04/29
phantom-deps	phantom-dep:amazon-cognito-identity-js	AI (phantom-deps): Conditional integration dep; phantom-dep heuristic fires on config references.	ai	2026/04/29
phantom-deps	phantom-dep:node-fetch	AI (phantom-deps): Conditional integration dep; phantom-dep heuristic fires on config references.	ai	2026/04/29

Versions (showing 21 of 21)

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.39	15 / 6	2026-03-20
2.1.32	15 / 6	2025-12-11
2.1.31	15 / 6	2025-12-11
2.1.28	15 / 6	2025-12-04
2.1.27	15 / 6	2025-12-04
2.1.26	15 / 6	2025-11-19
2.1.24	15 / 6	2025-11-19
2.1.23	15 / 6	2025-11-19
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

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

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

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

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

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

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

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

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

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

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

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.