@plusscommunities/pluss-maintenance-aws
Extension package to enable maintenance on Pluss Communities Platform
Supply chain provenance
Status for the latest visible version.
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
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): Common Node.js built-in wrapper; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:twilio | AI (phantom-deps): Declared dep used in AWS Lambda handlers; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:aws-sdk | AI (phantom-deps): Standard AWS SDK dep for Lambda; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:node-jose | AI (phantom-deps): Declared dep for JWT/JOSE operations; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Declared dep for HTTP requests; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:nodemailer | AI (phantom-deps): Declared dep for email; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:expo-server-sdk | AI (phantom-deps): Declared dep for push notifications; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:amazon-cognito-identity-js | AI (phantom-deps): Declared dep for Cognito auth; phantom-dep heuristic false positive. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.1.46 | 15 / 6 | |
| 2.1.45 | 15 / 6 | |
| 2.1.44 | 15 / 6 | |
| 2.1.43 | 15 / 6 | |
| 2.1.42 | 15 / 6 | |
| 2.1.41 | 15 / 6 | |
| 2.1.21 | 15 / 6 | |
| 2.1.20 | 15 / 6 | |
| 2.1.19 | 15 / 6 | |
| 2.1.18 | 15 / 6 | |
| 2.1.17 | 15 / 6 | |
| 2.1.16 | 15 / 6 | |
| 2.1.15 | 15 / 6 | |
| 2.1.14 | 15 / 6 | |
| 2.1.13 | 15 / 6 | |
| 2.1.12 | 15 / 6 | |
| 2.1.10 | 15 / 6 | |
| 2.1.9 | 15 / 6 | |
| 2.1.8 | 15 / 6 | |
| 2.1.7 | 15 / 6 | |
| 2.1.4 | 15 / 6 | |
| 2.1.3 | 15 / 6 | |
| 2.1.2 | 15 / 6 | |
| 2.1.1 | 15 / 6 | |
| 2.1.0 | 15 / 6 | |
| 2.0.3 | 14 / 6 | |
| 2.0.2 | 14 / 6 | |
| 2.0.1 | 14 / 3 |
v2.1.46
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pluss-thor) than the most recent previously approved version (pluss-aloys) on 2026-07-17, but pluss-thor is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.