@ocap/resolver
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/types.d.cts | AI (source-diff): Long-line .d.cts type declarations from bundler, not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm/types.d.mts | AI (source-diff): Long-line .d.mts type declarations from bundler, not obfuscated code. | ai | |
| phantom-deps | phantom-dep:@ocap/wallet | AI (phantom-deps): Same-org monorepo sibling, indirectly used. | ai | |
| phantom-deps | phantom-dep:@arcblock/did-ext | AI (phantom-deps): Used via config, same-org dependency. | ai |
Versions (showing 38 of 138)
| Version | Deps | Published |
|---|---|---|
| 1.18.165 | 12 / 1 | |
| 1.18.164 | 12 / 1 | |
| 1.18.163 | 12 / 1 | |
| 1.18.162 | 12 / 1 | |
| 1.18.161 | 12 / 1 | |
| 1.18.160 | 12 / 1 | |
| 1.18.159 | 12 / 1 | |
| 1.18.158 | 12 / 1 | |
| 1.18.157 | 12 / 1 | |
| 1.18.156 | 12 / 1 | |
| 1.18.155 | 12 / 1 | |
| 1.18.154 | 12 / 1 | |
| 1.18.153 | 12 / 1 | |
| 1.18.152 | 12 / 1 | |
| 1.18.151 | 12 / 1 | |
| 1.18.150 | 12 / 1 | |
| 1.18.149 | 12 / 1 | |
| 1.18.148 | 12 / 1 | |
| 1.18.147 | 12 / 1 | |
| 1.18.146 | 12 / 1 | |
| 1.18.145 | 12 / 1 | |
| 1.18.144 | 12 / 1 | |
| 1.18.143 | 12 / 1 | |
| 1.18.142 | 12 / 1 | |
| 1.18.140 | 12 / 1 | |
| 1.18.139 | 12 / 1 | |
| 1.18.138 | 12 / 1 | |
| 1.18.137 | 12 / 1 | |
| 1.18.136 | 12 / 1 | |
| 1.18.135 | 12 / 1 | |
| 1.18.134 | 12 / 1 | |
| 1.18.133 | 12 / 1 | |
| 1.18.132 | 12 / 1 | |
| 1.18.131 | 12 / 1 | |
| 1.18.130 | 12 / 1 | |
| 1.18.129 | 12 / 1 | |
| 1.18.128 | 12 / 1 | |
| 1.18.127 | 12 / 1 |
v1.18.165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.149
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.142
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.