@cdxgen/cdxgen 0.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +136 -0
- package/mod.d.ts +7 -0
- package/mod.js +22 -0
- package/package.json +42 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "{}"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright {yyyy} {name of copyright owner}
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,136 @@
|
|
|
1
|
+
# `@cdxgen/cdxgen` name placeholder
|
|
2
|
+
|
|
3
|
+
A minimal, deliberately inert package whose only job is to **create the
|
|
4
|
+
`@cdxgen/cdxgen` name on npm and JSR** so trusted publishing can be configured
|
|
5
|
+
against it.
|
|
6
|
+
|
|
7
|
+
Both registries attach a trusted publisher to an *existing* package. The
|
|
8
|
+
package therefore has to exist before the v13 release can publish via OIDC, and
|
|
9
|
+
the first publish has to use a token. That first publish is what this directory
|
|
10
|
+
is for.
|
|
11
|
+
|
|
12
|
+
The `@cyclonedx` namespace already has this set up for v12; none of that
|
|
13
|
+
configuration carries over to `@cdxgen`.
|
|
14
|
+
|
|
15
|
+
## What it deliberately does not do
|
|
16
|
+
|
|
17
|
+
- **No `bin`.** cdxgen's executable is called `cdxgen`. A placeholder shipping
|
|
18
|
+
an executable of that name would shadow the real tool for anyone who
|
|
19
|
+
installed it by accident.
|
|
20
|
+
- **Not published as `latest`.** `publishConfig.tag` is `placeholder`, so
|
|
21
|
+
`npm install @cdxgen/cdxgen` does not resolve to it. Between this publish and
|
|
22
|
+
the v13 release the package has no `latest` tag at all, and an install fails
|
|
23
|
+
with "no matching version" — which is the correct outcome, because there is
|
|
24
|
+
nothing here worth installing.
|
|
25
|
+
- **Version `0.0.1`**, so it sorts below `13.0.0` and never wins resolution.
|
|
26
|
+
|
|
27
|
+
## Step 1 — publish the placeholder with a token
|
|
28
|
+
|
|
29
|
+
Trusted publishing cannot be used for this first publish; that is the
|
|
30
|
+
bootstrapping problem it exists to solve.
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
cd ~/cdxgen-publish-placeholder
|
|
34
|
+
|
|
35
|
+
npm pack --dry-run # expect exactly: mod.js, README.md, LICENSE, package.json
|
|
36
|
+
|
|
37
|
+
npm login # or NODE_AUTH_TOKEN with publish rights on @cdxgen
|
|
38
|
+
npm publish # access + placeholder tag come from publishConfig
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
Verify no `latest` tag was created:
|
|
42
|
+
|
|
43
|
+
```bash
|
|
44
|
+
npm view @cdxgen/cdxgen dist-tags
|
|
45
|
+
# { placeholder: '0.0.1' } ← latest must be absent
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
## Step 2 — publish to JSR
|
|
49
|
+
|
|
50
|
+
JSR requires the `@cdxgen` scope to exist first — create it at
|
|
51
|
+
<https://jsr.io/new> if it does not. Then:
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
npx jsr publish
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
JSR has no dist-tag concept, so `0.0.1` becomes the only version until v13
|
|
58
|
+
publishes over it.
|
|
59
|
+
|
|
60
|
+
## Step 3 — configure the trusted publisher on npm
|
|
61
|
+
|
|
62
|
+
<https://www.npmjs.com/package/@cdxgen/cdxgen> → **Settings** → **Trusted
|
|
63
|
+
publisher** → GitHub Actions:
|
|
64
|
+
|
|
65
|
+
| Field | Value |
|
|
66
|
+
| ----- | ----- |
|
|
67
|
+
| Organization or user | `cdxgen` |
|
|
68
|
+
| Repository | `cdxgen` |
|
|
69
|
+
| Workflow filename | `npm-release.yml` |
|
|
70
|
+
| Environment | *(leave empty unless the release job declares one)* |
|
|
71
|
+
|
|
72
|
+
The workflow filename must match the file in `.github/workflows/` **exactly**,
|
|
73
|
+
and it must exist on the repository's default branch. A mismatch surfaces as a
|
|
74
|
+
403 at publish time with no explanation of which field is wrong.
|
|
75
|
+
|
|
76
|
+
## Step 4 — configure the trusted publisher on JSR
|
|
77
|
+
|
|
78
|
+
<https://jsr.io/@cdxgen/cdxgen/settings> → **GitHub repository** → link
|
|
79
|
+
`cdxgen/cdxgen`. JSR verifies the OIDC token's repository claim, so any
|
|
80
|
+
workflow in that repo with `id-token: write` can publish; there is no
|
|
81
|
+
per-workflow field to match.
|
|
82
|
+
|
|
83
|
+
## Step 5 — fix the real release workflow
|
|
84
|
+
|
|
85
|
+
`.github/workflows/npm-release.yml` in `cdxgen/cdxgen` still carries the v12
|
|
86
|
+
setup and will not authenticate against `@cdxgen`:
|
|
87
|
+
|
|
88
|
+
```yaml
|
|
89
|
+
- name: Use Node.js
|
|
90
|
+
uses: actions/setup-node@...
|
|
91
|
+
with:
|
|
92
|
+
registry-url: https://registry.npmjs.org/
|
|
93
|
+
scope: '@cyclonedx' # ← wrong namespace for v13
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
Two changes are needed, and the second is the one that silently breaks OIDC:
|
|
97
|
+
|
|
98
|
+
1. `scope: '@cyclonedx'` → `'@cdxgen'`, or drop it.
|
|
99
|
+
2. **Drop `registry-url` as well.** `setup-node` writes an `.npmrc` containing
|
|
100
|
+
`//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}` whenever
|
|
101
|
+
`registry-url` is set. npm prefers that token over the OIDC exchange, so the
|
|
102
|
+
publish either fails on an empty token or succeeds using a long-lived
|
|
103
|
+
secret — quietly defeating the point of trusted publishing.
|
|
104
|
+
|
|
105
|
+
The job already has `id-token: write`, which is the other half of the
|
|
106
|
+
requirement.
|
|
107
|
+
|
|
108
|
+
Also confirm the npm CLI version: OIDC publishing needs **npm >= 11.5.1**, and
|
|
109
|
+
the version bundled with a given Node release is often older. `npm install -g
|
|
110
|
+
npm@latest` before publishing, or pin a known-good version.
|
|
111
|
+
|
|
112
|
+
See `.github/workflows/publish.yml` here for the full shape.
|
|
113
|
+
|
|
114
|
+
## Step 6 — after v13.0.0 is released
|
|
115
|
+
|
|
116
|
+
Remove the placeholder tag so the package has no stray pointers:
|
|
117
|
+
|
|
118
|
+
```bash
|
|
119
|
+
npm dist-tag rm @cdxgen/cdxgen placeholder
|
|
120
|
+
npm view @cdxgen/cdxgen dist-tags # expect only: latest: 13.0.0
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
`0.0.1` stays published — npm unpublishing is restricted and the version is
|
|
124
|
+
harmless once `latest` exists.
|
|
125
|
+
|
|
126
|
+
## Verifying trusted publishing actually engaged
|
|
127
|
+
|
|
128
|
+
A successful OIDC publish attaches a provenance attestation. After the first
|
|
129
|
+
real release:
|
|
130
|
+
|
|
131
|
+
```bash
|
|
132
|
+
npm view @cdxgen/cdxgen dist.attestations
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
If that is empty, the publish used a token and the trusted-publisher path was
|
|
136
|
+
never exercised, whatever the workflow logs suggest.
|
package/mod.d.ts
ADDED
package/mod.js
ADDED
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Name placeholder for cdxgen v13.
|
|
3
|
+
*
|
|
4
|
+
* This package exists so that the `@cdxgen/cdxgen` name is registered on npm
|
|
5
|
+
* and JSR, which is a precondition for configuring trusted publishing (OIDC)
|
|
6
|
+
* on either registry: a trusted publisher is attached to an existing package,
|
|
7
|
+
* so the package has to be created before the real release can use it.
|
|
8
|
+
*
|
|
9
|
+
* It deliberately ships no CLI. cdxgen's binary is called `cdxgen`, and a
|
|
10
|
+
* placeholder that installs an executable of that name would shadow the real
|
|
11
|
+
* tool for anyone who installed this by mistake.
|
|
12
|
+
*
|
|
13
|
+
* @returns {string} A message naming the package to install instead
|
|
14
|
+
*/
|
|
15
|
+
export function placeholderNotice() {
|
|
16
|
+
return (
|
|
17
|
+
"@cdxgen/cdxgen is a name placeholder. cdxgen v13 has not been released " +
|
|
18
|
+
"under this name yet — install @cyclonedx/cdxgen instead."
|
|
19
|
+
);
|
|
20
|
+
}
|
|
21
|
+
|
|
22
|
+
export default placeholderNotice;
|
package/package.json
ADDED
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@cdxgen/cdxgen",
|
|
3
|
+
"version": "0.0.1",
|
|
4
|
+
"description": "Name placeholder for cdxgen v13. Install @cyclonedx/cdxgen until v13.0.0 is released.",
|
|
5
|
+
"license": "Apache-2.0",
|
|
6
|
+
"author": "Prabhu Subramanian <prabhu@appthreat.com>",
|
|
7
|
+
"homepage": "https://cdxgen.github.io/cdxgen/",
|
|
8
|
+
"repository": {
|
|
9
|
+
"type": "git",
|
|
10
|
+
"url": "git+https://github.com/cdxgen/cdxgen.git"
|
|
11
|
+
},
|
|
12
|
+
"bugs": {
|
|
13
|
+
"url": "https://github.com/cdxgen/cdxgen/issues"
|
|
14
|
+
},
|
|
15
|
+
"type": "module",
|
|
16
|
+
"exports": {
|
|
17
|
+
".": {
|
|
18
|
+
"types": "./mod.d.ts",
|
|
19
|
+
"default": "./mod.js"
|
|
20
|
+
}
|
|
21
|
+
},
|
|
22
|
+
"files": [
|
|
23
|
+
"mod.js",
|
|
24
|
+
"mod.d.ts",
|
|
25
|
+
"README.md",
|
|
26
|
+
"LICENSE"
|
|
27
|
+
],
|
|
28
|
+
"engines": {
|
|
29
|
+
"node": ">=24"
|
|
30
|
+
},
|
|
31
|
+
"publishConfig": {
|
|
32
|
+
"access": "public",
|
|
33
|
+
"tag": "placeholder"
|
|
34
|
+
},
|
|
35
|
+
"keywords": [
|
|
36
|
+
"sbom",
|
|
37
|
+
"cyclonedx",
|
|
38
|
+
"cdxgen",
|
|
39
|
+
"placeholder"
|
|
40
|
+
],
|
|
41
|
+
"types": "./mod.d.ts"
|
|
42
|
+
}
|