@arcblock/did-connect-react
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 | missing-githead | AI (provenance): Major version refactor; single missing gitHead on a v4 rewrite from a trusted publisher with 630 approvals. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @arcblock/did-connect-core is the new core package in this refactored architecture; not a suspicious addition. | ai | |
| source-diff | source-size-dropped | AI (source-diff): v4 is a deliberate refactor delegating logic to did-connect-core; size drop reflects removed deps, not stub replacement. | ai | |
| provenance | no-provenance | AI (provenance): ArcBlock org consistently publishes without Sigstore provenance; stable false positive for this package family. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Used for key encoding/decoding in a crypto utility; not obfuscation or payload hiding. | ai | |
| phantom-deps | phantom-dep:color-convert | AI (phantom-deps): Config-file reference only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@iconify-icons/logos | AI (phantom-deps): Config-file reference only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@blocklet/constant | AI (phantom-deps): Config-file reference only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mdi-material-ui | AI (phantom-deps): Config-file reference only; stable false positive for this package. | ai |
Versions (showing 9 of 118)
| Version | Deps | Published |
|---|---|---|
| 3.1.8 | 30 / 2 | |
| 3.1.7 | 30 / 2 | |
| 3.1.6 | 30 / 2 | |
| 3.1.5 | 30 / 2 | |
| 3.1.4 | 30 / 2 | |
| 3.1.3 | 30 / 2 | |
| 3.1.2 | 30 / 2 | |
| 3.1.1 | 30 / 2 | |
| 3.1.0 | 30 / 2 |
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.