← Home

@plusscommunities/pluss-core-app

Core extension package for Pluss Communities platform

26
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

pluss-thorpluss_pspluss_devpluss-aloys

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Established package with clean history; missing gitHead likely reflects a CI/publish environment change, not malicious activity. ai
provenance no-provenance AI (provenance): Long-standing package without provenance attestation; consistent with its publish history. ai

Versions (showing 26 of 26)

Version Deps Published
8.0.38 0 / 1
8.0.37 0 / 1
8.0.36 0 / 1
8.0.35 0 / 1
8.0.31 0 / 1
8.0.29 0 / 1
8.0.28 0 / 1
8.0.27 0 / 1
8.0.26 0 / 1
8.0.24 0 / 1
8.0.20 0 / 1
8.0.19 0 / 1
8.0.18 0 / 1
8.0.17 0 / 1
8.0.16 0 / 1
8.0.11 0 / 1
8.0.10 0 / 1
8.0.9 0 / 1
8.0.6 0 / 1
8.0.5 0 / 1
8.0.4 0 / 1
8.0.3 0 / 1
8.0.2 0 / 1
8.0.1 0 / 1
8.0.0 0 / 1
7.1.16 0 / 1

v8.0.38

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.0.37

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pluss-thor → pluss-aloys (on 2026-07-07, known maintainer) provenance

This version was published by a different npm account (pluss-aloys) than the most recent previously approved version (pluss-thor) on 2026-07-07, 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.

v8.0.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.0.19

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.0.18

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.0.17

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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-thor.

v8.0.16

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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-thor.