@plusscommunities/pluss-newsletter-app
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established org package with clean history; missing gitHead alone is insufficient to block given no other risk signals. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.0.12 | 0 / 1 | |
| 8.0.9 | 0 / 1 | |
| 8.0.8 | 0 / 1 | |
| 8.0.6 | 0 / 1 | |
| 8.0.4 | 0 / 1 | |
| 8.0.3 | 0 / 1 | |
| 8.0.2 | 0 / 1 | |
| 8.0.1 | 0 / 1 | |
| 7.0.7 | 0 / 1 |
v8.0.12
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pluss-aloys.
This version was published by a different npm account (pluss-aloys) than the most recent previously approved version (pluss-thor) on 2026-07-14, but pluss-aloys 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.