@fairmint/open-captable-protocol-daml-js
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Fairmint migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable org-level transition. | ai | |
| phantom-deps | phantom-dep:@daml/ledger | AI (phantom-deps): Declared as peer dependency; not directly imported in lib code is expected for peer deps. | ai | |
| phantom-deps | phantom-dep:@fairmint/canton-node-sdk | AI (phantom-deps): Same-org dep used in scripts/tooling, not directly imported in lib — stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Proprietary internal package; no provenance is consistent across all versions. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Intentionally proprietary/closed-source package from Fairmint org; stable across versions. | ai |
Versions (showing 46 of 163)
| Version | Deps | Published |
|---|---|---|
| 0.2.42 | 3 / 5 | |
| 0.2.41 | 3 / 5 | |
| 0.2.40 | 3 / 5 | |
| 0.2.39 | 3 / 5 | |
| 0.2.38 | 3 / 5 | |
| 0.2.37 | 3 / 5 | |
| 0.2.36 | 3 / 5 | |
| 0.2.35 | 3 / 5 | |
| 0.2.34 | 3 / 5 | |
| 0.2.33 | 3 / 5 | |
| 0.2.32 | 3 / 5 | |
| 0.2.30 | 3 / 4 | |
| 0.2.29 | 3 / 4 | |
| 0.2.28 | 3 / 4 | |
| 0.2.27 | 3 / 4 | |
| 0.2.25 | 3 / 4 | |
| 0.2.24 | 3 / 4 | |
| 0.2.23 | 3 / 4 | |
| 0.2.22 | 3 / 4 | |
| 0.2.21 | 3 / 4 | |
| 0.2.20 | 3 / 4 | |
| 0.2.19 | 3 / 4 | |
| 0.2.18 | 3 / 4 | |
| 0.2.17 | 3 / 4 | |
| 0.2.16 | 3 / 4 | |
| 0.2.15 | 3 / 4 | |
| 0.2.14 | 3 / 4 | |
| 0.2.13 | 3 / 4 | |
| 0.2.12 | 3 / 4 | |
| 0.2.11 | 3 / 4 | |
| 0.0.41 | 3 / 4 | |
| 0.0.40 | 3 / 4 | |
| 0.0.39 | 3 / 4 | |
| 0.0.38 | 3 / 4 | |
| 0.0.37 | 3 / 4 | |
| 0.0.36 | 3 / 4 | |
| 0.0.35 | 3 / 4 | |
| 0.0.34 | 3 / 4 | |
| 0.0.33 | 3 / 4 | |
| 0.0.31 | 1 / 0 | |
| 0.0.30 | 1 / 0 | |
| 0.0.29 | 1 / 0 | |
| 0.0.25 | 1 / 0 | |
| 0.0.24 | 1 / 0 | |
| 0.0.22 | 1 / 0 | |
| 0.0.2 | 1 / 4 |
v0.2.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.