@plusscommunities/pluss-maintenance-aws-food
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 — the axios compromise (March 2026) relied on exactly this gap.
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): Node built-in polyfill package; commonly declared but not directly imported in serverless AWS packages. | ai | |
| phantom-deps | phantom-dep:twilio | AI (phantom-deps): Optional integration dependency; pattern is stable for this multi-integration serverless package. | ai | |
| phantom-deps | phantom-dep:aws-sdk | AI (phantom-deps): AWS SDK commonly used indirectly via wrappers in serverless packages. | ai | |
| phantom-deps | phantom-dep:node-jose | AI (phantom-deps): Optional JWT/crypto integration; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Optional HTTP integration; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:nodemailer | AI (phantom-deps): Optional email integration; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:expo-server-sdk | AI (phantom-deps): Optional push notification integration; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:amazon-cognito-identity-js | AI (phantom-deps): Optional Cognito integration; stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 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 |
v2.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.21
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.