@polkadot/extension-dapp
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 established Polkadot ecosystem CI publisher; transition from polkadotjs is a known org-level migration. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): paritytech-ci addition is consistent with org-wide CI publisher consolidation, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy reflects upstream project cadence, not account takeover; publisher track record is clean. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.63.1 | 4 / 0 | |
| 0.62.6 | 4 / 0 | |
| 0.62.5 | 4 / 0 | |
| 0.62.4 | 4 / 0 | |
| 0.62.3 | 4 / 0 | |
| 0.62.2 | 4 / 0 | |
| 0.62.1 | 4 / 0 | |
| 0.61.7 | 4 / 0 | |
| 0.61.6 | 4 / 0 | |
| 0.61.5 | 4 / 0 | |
| 0.61.4 | 4 / 0 | |
| 0.61.3 | 4 / 0 | |
| 0.61.2 | 4 / 0 | |
| 0.61.1 | 4 / 0 | |
| 0.60.1 | 4 / 0 | |
| 0.59.2 | 4 / 0 | |
| 0.59.1 | 4 / 0 |
v0.63.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-31. 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.
v0.62.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.