@polkadot/ui-shared
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 10 of 10)
| 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 |
v3.16.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.