@plusscommunities/pluss-core-aws
Core extension package for 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:pg | AI (phantom-deps): Consistent with other longstanding accepted phantom-dep findings for this package. | ai | |
| dependencies | unvetted-dep:@plusscommunities/pluss-llm-telemetry-aws | AI (dependencies): Same-org sibling package, normal internal monorepo dependency. | ai | |
| phantom-deps | phantom-dep:nodemailer | AI (phantom-deps): Same platform core library pattern; declared for downstream use. | ai | |
| phantom-deps | phantom-dep:twilio | AI (phantom-deps): Platform core library; deps declared for downstream consumers, not direct imports. Stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@aws/dynamodb-auto-marshaller | AI (phantom-deps): Same platform core library pattern; declared for downstream use. | ai | |
| phantom-deps | phantom-dep:amazon-cognito-identity-js | AI (phantom-deps): Same platform core library pattern; declared for downstream use. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Same platform core library pattern; declared for downstream use. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.0.33 | 18 / 3 | |
| 2.0.27 | 17 / 3 | |
| 2.0.26 | 17 / 3 | |
| 2.0.24 | 15 / 3 | |
| 2.0.23 | 15 / 3 | |
| 2.0.22 | 15 / 3 | |
| 2.0.21 | 15 / 3 | |
| 2.0.20 | 15 / 3 | |
| 2.0.19 | 15 / 3 | |
| 2.0.18 | 15 / 3 | |
| 2.0.17 | 15 / 3 | |
| 2.0.14 | 14 / 3 | |
| 2.0.11 | 14 / 3 | |
| 2.0.10 | 14 / 3 | |
| 2.0.9 | 14 / 3 | |
| 2.0.8 | 14 / 3 | |
| 2.0.7 | 14 / 3 | |
| 2.0.5 | 14 / 3 | |
| 2.0.4 | 14 / 3 | |
| 2.0.3 | 14 / 3 | |
| 2.0.1 | 14 / 3 |
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.