@plusscommunities/pluss-newsletter-aws-newsa
Extension package to enable newsletter 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): Node built-in polyfill package; commonly declared but resolved via Node runtime. | ai | |
| phantom-deps | phantom-dep:aws-sdk | AI (phantom-deps): AWS SDK likely used transitively via pluss-core-aws; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:twilio | AI (phantom-deps): Likely used indirectly through shared core module; stable false positive. | ai | |
| phantom-deps | phantom-dep:node-jose | AI (phantom-deps): JWT/crypto utility likely used via core module; stable false positive. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): HTTP utility likely used via core module; stable false positive. | ai | |
| phantom-deps | phantom-dep:nodemailer | AI (phantom-deps): Email utility consistent with newsletter package purpose; stable false positive. | ai | |
| phantom-deps | phantom-dep:expo-server-sdk | AI (phantom-deps): Push notification SDK consistent with platform purpose; stable false positive. | ai | |
| phantom-deps | phantom-dep:amazon-cognito-identity-js | AI (phantom-deps): Auth SDK likely used via core module; stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.10 | 14 / 6 | |
| 2.0.9 | 14 / 6 | |
| 2.0.7 | 14 / 6 | |
| 2.0.6 | 14 / 6 | |
| 2.0.5 | 14 / 6 | |
| 2.0.4 | 14 / 6 | |
| 2.0.3 | 14 / 6 | |
| 2.0.2 | 14 / 6 |
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.