@blocklet/did-space-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): ArcBlock monorepo package; no provenance is consistent across all versions and poses no direct security risk. | ai | |
| phantom-deps | phantom-dep:@mui/lab | AI (phantom-deps): Listed as runtime dep; likely used transitively or re-exported in bundled dist. | ai | |
| phantom-deps | phantom-dep:p-wait-for | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic fires on bundled packages. | ai | |
| phantom-deps | phantom-dep:@mui/system | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic fires on bundled packages. | ai | |
| phantom-deps | phantom-dep:react-error-boundary | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic fires on bundled packages. | ai |
Versions (showing 51 of 65)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 17 / 41 | |
| 1.2.23 | 17 / 41 | |
| 1.2.22 | 17 / 41 | |
| 1.2.20 | 17 / 41 | |
| 1.2.17 | 17 / 41 | |
| 1.2.14 | 17 / 41 | |
| 1.2.11 | 17 / 41 | |
| 1.2.10 | 17 / 41 | |
| 1.2.8 | 17 / 41 | |
| 1.2.7 | 17 / 41 | |
| 1.2.6 | 17 / 41 | |
| 1.2.5 | 17 / 41 | |
| 1.2.4 | 17 / 41 | |
| 1.2.3 | 17 / 41 | |
| 1.2.2 | 17 / 41 | |
| 1.2.1 | 17 / 41 | |
| 1.2.0 | 17 / 41 | |
| 1.1.35 | 17 / 41 | |
| 1.1.34 | 17 / 41 | |
| 1.1.33 | 17 / 41 | |
| 1.1.32 | 17 / 41 | |
| 1.1.31 | 17 / 41 | |
| 1.1.30 | 17 / 41 | |
| 1.1.29 | 17 / 41 | |
| 1.1.28 | 17 / 41 | |
| 1.1.27 | 17 / 41 | |
| 1.1.26 | 17 / 41 | |
| 1.1.25 | 17 / 41 | |
| 1.1.24 | 17 / 41 | |
| 1.1.23 | 17 / 41 | |
| 1.1.22 | 17 / 41 | |
| 1.1.21 | 17 / 41 | |
| 1.1.19 | 17 / 41 | |
| 1.1.18 | 17 / 41 | |
| 1.1.17 | 17 / 41 | |
| 1.1.16 | 17 / 41 | |
| 1.1.15 | 17 / 41 | |
| 1.1.14 | 17 / 41 | |
| 1.1.13 | 17 / 41 | |
| 1.1.12 | 17 / 41 | |
| 1.1.11 | 17 / 41 | |
| 1.1.10 | 17 / 41 | |
| 1.1.9 | 17 / 41 | |
| 1.1.8 | 17 / 41 | |
| 1.1.7 | 17 / 41 | |
| 1.1.6 | 17 / 41 | |
| 1.1.5 | 17 / 41 | |
| 1.1.4 | 17 / 41 | |
| 1.1.3 | 17 / 41 | |
| 1.1.2 | 17 / 41 | |
| 1.1.1 | 17 / 41 |
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.