@arcblock/did-connect
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Used for cryptographic key encode/decode utilities alongside tweetnacl; not obfuscation. | ai | |
| phantom-deps | phantom-dep:color-convert | AI (phantom-deps): Declared dep referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mdi-material-ui | AI (phantom-deps): Declared dep referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@iconify-icons/logos | AI (phantom-deps): Declared dep referenced in config files; stable false positive for this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 3.0.43 | 30 / 2 | |
| 3.0.42 | 30 / 2 | |
| 3.0.41 | 30 / 2 | |
| 3.0.39 | 30 / 2 | |
| 3.0.38 | 30 / 2 | |
| 3.0.37 | 30 / 2 | |
| 3.0.36 | 30 / 2 | |
| 3.0.35 | 30 / 2 | |
| 3.0.34 | 30 / 2 | |
| 3.0.33 | 30 / 2 | |
| 3.0.32 | 30 / 2 | |
| 3.0.31 | 30 / 2 | |
| 3.0.30 | 30 / 2 | |
| 3.0.29 | 30 / 2 | |
| 3.0.28 | 30 / 2 | |
| 3.0.27 | 30 / 2 | |
| 3.0.26 | 30 / 2 | |
| 3.0.25 | 30 / 2 | |
| 3.0.24 | 30 / 2 | |
| 3.0.23 | 30 / 2 | |
| 3.0.22 | 30 / 2 | |
| 3.0.21 | 30 / 2 | |
| 3.0.20 | 30 / 2 | |
| 3.0.19 | 30 / 2 | |
| 3.0.17 | 30 / 2 | |
| 3.0.16 | 29 / 2 | |
| 3.0.15 | 29 / 2 | |
| 3.0.14 | 29 / 2 | |
| 3.0.13 | 29 / 2 | |
| 3.0.12 | 29 / 2 | |
| 3.0.11 | 29 / 2 | |
| 3.0.10 | 29 / 2 | |
| 3.0.9 | 29 / 2 | |
| 3.0.8 | 29 / 2 | |
| 3.0.7 | 29 / 2 | |
| 3.0.6 | 29 / 2 | |
| 3.0.5 | 29 / 2 | |
| 3.0.4 | 29 / 2 | |
| 3.0.3 | 29 / 2 | |
| 3.0.2 | 29 / 2 | |
| 3.0.1 | 29 / 2 | |
| 3.0.0 | 29 / 2 |
v3.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.