@open-captable-protocol/canton
A TypeScript SDK for interacting with the Open CapTable Protocol (OCP) Factory contract on Canton blockchain
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@open-captable-protocol/canton | AI (phantom-deps): Package listing itself as a dependency is a versioning artifact, not a real phantom dep issue. | ai | |
| phantom-deps | phantom-dep:@daml/types | AI (phantom-deps): DAML types referenced in config; stable pattern for Canton SDK. | ai | |
| phantom-deps | phantom-dep:@daml/ledger | AI (phantom-deps): DAML ledger referenced in config; stable pattern for Canton SDK. | ai |
Versions (showing 51 of 357)
| Version | Deps | Published |
|---|---|---|
| 0.5.8 | 5 / 23 | |
| 0.5.7 | 5 / 23 | |
| 0.5.6 | 5 / 23 | |
| 0.5.5 | 5 / 23 | |
| 0.5.4 | 5 / 23 | |
| 0.5.3 | 5 / 23 | |
| 0.5.2 | 5 / 23 | |
| 0.5.1 | 5 / 23 | |
| 0.4.1 | 5 / 23 | |
| 0.2.306 | 5 / 23 | |
| 0.2.305 | 5 / 23 | |
| 0.2.304 | 5 / 23 | |
| 0.2.303 | 5 / 23 | |
| 0.2.302 | 5 / 24 | |
| 0.2.301 | 5 / 24 | |
| 0.2.300 | 5 / 24 | |
| 0.2.299 | 5 / 24 | |
| 0.2.298 | 5 / 24 | |
| 0.2.297 | 5 / 24 | |
| 0.2.296 | 5 / 24 | |
| 0.2.295 | 5 / 24 | |
| 0.2.294 | 5 / 24 | |
| 0.2.293 | 5 / 24 | |
| 0.2.292 | 5 / 24 | |
| 0.2.291 | 5 / 24 | |
| 0.2.289 | 5 / 24 | |
| 0.2.288 | 5 / 24 | |
| 0.2.287 | 5 / 24 | |
| 0.2.286 | 5 / 24 | |
| 0.2.285 | 5 / 24 | |
| 0.2.284 | 5 / 24 | |
| 0.2.283 | 5 / 24 | |
| 0.2.282 | 5 / 24 | |
| 0.2.281 | 5 / 24 | |
| 0.2.280 | 5 / 24 | |
| 0.2.279 | 5 / 24 | |
| 0.2.278 | 5 / 24 | |
| 0.2.277 | 5 / 24 | |
| 0.2.276 | 5 / 24 | |
| 0.2.275 | 5 / 24 | |
| 0.2.274 | 5 / 24 | |
| 0.2.273 | 5 / 24 | |
| 0.2.272 | 5 / 24 | |
| 0.2.271 | 5 / 24 | |
| 0.2.270 | 5 / 24 | |
| 0.2.269 | 5 / 24 | |
| 0.2.268 | 5 / 24 | |
| 0.2.267 | 5 / 24 | |
| 0.2.266 | 5 / 24 | |
| 0.2.265 | 5 / 24 | |
| 0.2.264 | 5 / 24 |
v0.5.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.306
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.305
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.304
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.303
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.302
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.301
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.300
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.299
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.298
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.297
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.296
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.295
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.294
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.293
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.292
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.291
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.289
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.288
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.287
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.286
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.285
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.284
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.283
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.282
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.281
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.280
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.279
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.278
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.277
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.276
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.275
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.274
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.273
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.272
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.271
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.270
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.269
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.268
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.267
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.266
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.265
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.264
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.