@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, so a manually published version cannot be tied back to a reviewed commit.
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 45 of 45)
| 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 | |
| 0.58.10 | 4 / 0 | |
| 0.58.9 | 4 / 0 | |
| 0.58.8 | 4 / 0 | |
| 0.58.7 | 4 / 0 | |
| 0.58.6 | 4 / 0 | |
| 0.58.5 | 4 / 0 | |
| 0.58.4 | 4 / 0 | |
| 0.58.3 | 4 / 0 | |
| 0.58.2 | 4 / 0 | |
| 0.58.1 | 4 / 0 | |
| 0.57.1 | 4 / 0 | |
| 0.56.2 | 4 / 0 | |
| 0.56.1 | 4 / 0 | |
| 0.55.1 | 4 / 0 | |
| 0.54.1 | 4 / 0 | |
| 0.53.1 | 4 / 0 | |
| 0.52.3 | 4 / 0 | |
| 0.52.2 | 4 / 0 | |
| 0.52.1 | 4 / 0 | |
| 0.51.1 | 4 / 0 | |
| 0.50.1 | 4 / 0 | |
| 0.49.3 | 4 / 0 | |
| 0.49.2 | 4 / 0 | |
| 0.49.1 | 4 / 0 | |
| 0.48.2 | 4 / 0 | |
| 0.48.1 | 4 / 0 | |
| 0.47.6 | 4 / 0 | |
| 0.47.5 | 4 / 0 |
v0.58.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.