← Home

@team-plain/ui-components

UI component builder helpers for Plain

8
Versions
MIT
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

emanuelatplainjesushernandezmattvagnijordrakefredninjapmihaylov-plaindleylandthinhninjayoumnasirgijuandlljamesacsjacobdcutts13mspq_plainrosieollerenshawmcmillandimitraszeliseheinrevettndom91ch2ch3dustinako

Keywords

plainui-componentstypescriptcustomer-support

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Publish-env change only; no code/dep/script change vs prior approved version. ai
maintainer-change maintainer-added AI (maintainer-change): Org-scoped package; roster change consistent with team transition, no malicious diff. ai
maintainer-change maintainer-removed AI (maintainer-change): Paired with maintainer-added roster update; benign for this trusted org package. ai
provenance no-provenance AI (provenance): Scoped org package with no other risk signals; missing provenance alone is not disqualifying. ai

Versions (showing 8 of 8)

Version Deps Published
5.0.0 0 / 3
4.0.1 0 / 3
4.0.0 0 / 3
3.0.0 0 / 3
2.0.1 0 / 3
2.0.0 0 / 2
1.0.0 0 / 2
0.1.0 0 / 2

v5.0.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mattvagni.

INFO No provenance attestation provenance

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

v4.0.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mattvagni.

INFO No provenance attestation provenance

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