← Home

@polkadot/ui-shared

npm Repository Homepage
22
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

jacogrpolkadotjsparitytech-ci

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): paritytech-ci is the Parity Technologies CI account with strong track record; org-level migration from polkadotjs is expected. ai
maintainer-change maintainer-added AI (maintainer-change): paritytech-ci addition reflects org CI migration, not a suspicious takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by org migration is consistent with a legitimate ownership transfer for this package. ai

Versions (showing 22 of 22)

Version Deps Published
3.16.7 2 / 0
3.16.4 2 / 0
3.16.3 2 / 0
3.16.2 2 / 0
3.16.1 2 / 0
3.15.4 2 / 0
3.15.3 2 / 0
3.15.2 2 / 0
3.15.1 2 / 0
3.14.1 2 / 0
3.13.1 2 / 0
3.12.2 2 / 0
3.12.1 2 / 0
3.11.3 2 / 0
3.11.2 2 / 0
3.11.1 2 / 0
3.10.1 2 / 0
3.9.1 2 / 0
3.8.3 2 / 0
3.8.2 2 / 0
3.8.1 2 / 0
3.7.1 2 / 0

v3.13.1

1 finding
LOW No provenance attestation provenance

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

v3.12.2

1 finding
LOW No provenance attestation provenance

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

v3.12.1

1 finding
LOW No provenance attestation provenance

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

v3.11.3

1 finding
LOW No provenance attestation provenance

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

v3.11.2

1 finding
LOW No provenance attestation provenance

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

v3.11.1

1 finding
LOW No provenance attestation provenance

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

v3.10.1

1 finding
LOW No provenance attestation provenance

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

v3.9.1

1 finding
LOW No provenance attestation provenance

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

v3.8.3

1 finding
LOW No provenance attestation provenance

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

v3.8.2

1 finding
LOW No provenance attestation provenance

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

v3.8.1

1 finding
LOW No provenance attestation provenance

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

v3.7.1

1 finding
LOW No provenance attestation provenance

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