@fairmint/canton-node-sdk
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Build-time tool used in scripts; correctly declared as runtime dep. | ai | |
| phantom-deps | phantom-dep:openapi-typescript | AI (phantom-deps): Build-time code generator; correctly declared as runtime dep. | ai | |
| phantom-deps | phantom-dep:openapi-fetch | AI (phantom-deps): Build-time tool used in scripts; correctly declared as runtime dep. | ai |
Versions (showing 51 of 106)
| Version | Deps | Published |
|---|---|---|
| 0.0.134 | 10 / 21 | |
| 0.0.133 | 10 / 21 | |
| 0.0.132 | 10 / 21 | |
| 0.0.131 | 10 / 21 | |
| 0.0.130 | 10 / 21 | |
| 0.0.129 | 10 / 21 | |
| 0.0.128 | 10 / 21 | |
| 0.0.127 | 10 / 21 | |
| 0.0.126 | 10 / 21 | |
| 0.0.125 | 10 / 21 | |
| 0.0.124 | 10 / 21 | |
| 0.0.123 | 10 / 21 | |
| 0.0.122 | 11 / 21 | |
| 0.0.121 | 11 / 21 | |
| 0.0.120 | 11 / 21 | |
| 0.0.119 | 9 / 21 | |
| 0.0.118 | 7 / 21 | |
| 0.0.117 | 7 / 21 | |
| 0.0.116 | 7 / 21 | |
| 0.0.115 | 7 / 21 | |
| 0.0.114 | 7 / 21 | |
| 0.0.113 | 7 / 21 | |
| 0.0.112 | 7 / 21 | |
| 0.0.111 | 7 / 21 | |
| 0.0.110 | 7 / 21 | |
| 0.0.109 | 7 / 21 | |
| 0.0.108 | 7 / 21 | |
| 0.0.107 | 7 / 21 | |
| 0.0.106 | 7 / 21 | |
| 0.0.105 | 7 / 21 | |
| 0.0.104 | 7 / 21 | |
| 0.0.103 | 7 / 21 | |
| 0.0.102 | 7 / 21 | |
| 0.0.101 | 7 / 21 | |
| 0.0.100 | 7 / 21 | |
| 0.0.99 | 7 / 17 | |
| 0.0.98 | 7 / 17 | |
| 0.0.97 | 7 / 17 | |
| 0.0.96 | 7 / 17 | |
| 0.0.95 | 7 / 17 | |
| 0.0.94 | 7 / 17 | |
| 0.0.93 | 7 / 17 | |
| 0.0.92 | 7 / 17 | |
| 0.0.91 | 7 / 17 | |
| 0.0.90 | 7 / 17 | |
| 0.0.89 | 6 / 16 | |
| 0.0.88 | 6 / 16 | |
| 0.0.87 | 6 / 16 | |
| 0.0.86 | 6 / 16 | |
| 0.0.85 | 6 / 16 | |
| 0.0.84 | 6 / 16 |
v0.0.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.