@plusscommunities/pluss-newsletter-aws-newsb
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): Common declared-but-not-directly-imported pattern in AWS Lambda monorepo packages. | ai | |
| phantom-deps | phantom-dep:twilio | AI (phantom-deps): Declared utility dep; phantom heuristic fires on conditional/indirect usage in this package. | ai | |
| phantom-deps | phantom-dep:aws-sdk | AI (phantom-deps): aws-sdk commonly used indirectly via SDK wrappers in Lambda packages. | ai | |
| phantom-deps | phantom-dep:node-jose | AI (phantom-deps): Stable false positive for this monorepo-style AWS package. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Stable false positive for this monorepo-style AWS package. | ai | |
| phantom-deps | phantom-dep:nodemailer | AI (phantom-deps): Stable false positive for this monorepo-style AWS package. | ai | |
| phantom-deps | phantom-dep:expo-server-sdk | AI (phantom-deps): Stable false positive for this monorepo-style AWS package. | ai | |
| phantom-deps | phantom-dep:amazon-cognito-identity-js | AI (phantom-deps): Stable false positive for this monorepo-style AWS package. | 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. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.