← Home

@adobe/uix-guest

npm Repository Homepage
17
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

marbectripodgarthdblazdadobe-adminpatrickfultontrieloffkrisnyedcpfsdknatebaldwindevongovettaspro83symanovidpfisterstefan-guggisbergrofekptdobeadobehallsfullcolorcoderdjaeggidylandepassmhaackamol-anandstopp-adobenamaroradotenduh_schmidtasthabh23zdahbituicufmeschbe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Established Adobe SDK package; sparse README/keywords are a style choice, not spam indicators. ai
provenance no-provenance AI (provenance): Adobe org package with long history; lack of Sigstore attestation is common and not a risk here. ai

Versions (showing 17 of 17)

Version Deps Published
1.1.10 3 / 0
1.1.9 3 / 0
1.1.8 3 / 0
1.1.7 3 / 0
1.1.6 3 / 0
1.1.5 3 / 0
1.1.4 3 / 0
1.1.3 3 / 0
1.1.2 3 / 0
1.1.1 3 / 0
1.1.0 3 / 0
1.0.5 3 / 0
1.0.4 3 / 0
1.0.3 3 / 0
1.0.2 3 / 0
1.0.1 3 / 0
1.0.0 3 / 0

v1.1.10

1 finding
INFO No provenance attestation provenance

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

v1.0.1

1 finding
INFO No provenance attestation provenance

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

v1.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.