Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
31 commits
Select commit Hold shift + click to select a range
fd0f044
Add GeoIP and GeoLite web services spec
oschwald Sep 22, 2026
aa6653b
Add minFraud web services spec
oschwald Sep 22, 2026
4c64034
Add account and download API specs
oschwald Sep 22, 2026
2f99486
Detect removed and renamed bundles in CI
oschwald Sep 24, 2026
5129765
Remove ignored HEAD Content-Type header
oschwald Sep 24, 2026
5ae3d48
Correct the default string limit wording
oschwald Sep 24, 2026
8f96f9f
Use a valid email domain first-seen date
oschwald Sep 24, 2026
8e99759
Align disposition reasons with rule labels
oschwald Sep 24, 2026
c4e038f
Clarify the illustrative response examples
oschwald Sep 24, 2026
3f62af8
Describe valid device IP address formats
oschwald Sep 24, 2026
6bf086c
Require all disposition update keys
oschwald Sep 24, 2026
dc1e94d
Allow future continent response codes
oschwald Sep 24, 2026
b0feeaf
Align AVS characters with public clients
oschwald Sep 24, 2026
eb51bfb
Clarify GeoLite account object availability
oschwald Sep 24, 2026
39124ca
Specify disposition update sort direction
oschwald Sep 24, 2026
adf0dca
Clarify the event time recommendation
oschwald Sep 24, 2026
5868857
Allow bodyless minFraud server errors
oschwald Sep 24, 2026
f6a8da5
Remove the undocumented GeoIP service error
oschwald Sep 24, 2026
f1ade1e
Describe privacy exclusion rate limiting
oschwald Sep 24, 2026
6659863
Describe geofeed report rate limiting
oschwald Sep 24, 2026
9313dee
Describe both causes of download rate limits
oschwald Sep 24, 2026
bfbdc68
Use generic Basic authentication descriptions
oschwald Sep 24, 2026
eb08fa3
Limit HTTP error body claims to documented APIs
oschwald Sep 24, 2026
85c504e
Remove server email normalization promises
oschwald Sep 24, 2026
a26e7b2
Remove the webhook acknowledgement claim
oschwald Sep 24, 2026
795c76f
Remove the cursor precision guarantee
oschwald Sep 24, 2026
fb9cdb1
Document the transaction report body limit
oschwald Sep 24, 2026
ce17682
Document the license validation body limit
oschwald Sep 24, 2026
f910659
Describe NUL restrictions on report fields
oschwald Sep 24, 2026
7cbe1f9
Describe IPv6 forms of privacy exclusions
oschwald Sep 24, 2026
ad00cda
Revert "Remove the undocumented GeoIP service error"
oschwald Sep 24, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
version: 2
updates:
- package-ecosystem: npm
directory: /
schedule:
interval: weekly
day: monday
time: "14:00"
groups:
minor-and-patch:
patterns:
- "*"
update-types:
- minor
- patch
cooldown:
default-days: 7
- package-ecosystem: github-actions
directory: /
schedule:
interval: weekly
day: monday
time: "14:00"
cooldown:
default-days: 7
38 changes: 38 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
name: CI
permissions:
contents: read

on:
push:
branches:
- main
pull_request:
workflow_dispatch:

jobs:
lint:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false

- name: Setup mise
uses: jdx/mise-action@3c2e0cf82a5b2e5249f0d3635a4d83d0ae861518 # v4.2.5

- name: Install dependencies
run: pnpm install --frozen-lockfile

- name: Lint files
run: precious lint --all

- name: Check that the bundles are current
run: |
rm -rf bundled
pnpm run bundle

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This check writes the bundles into the existing bundled/ directory. If an API is removed or renamed in redocly.yaml, its old bundled/*.yaml stays on disk. pnpm run bundle does not touch it, git diff --exit-code passes, and //go:embed bundled/*.yaml keeps shipping the old spec.

Suggestion: run rm -rf bundled before pnpm run bundle.

馃 Comment by Claude (Claude Code) on behalf of Will.

@oschwald oschwald Sep 24, 2026 •

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed by deleting the output directory before bundling and comparing the result against HEAD after marking new files intent-to-add. Verified unchanged bundles pass and added, removed, and renamed outputs each fail the check.

Commits: 2f99486.

馃 Response by Codex on behalf of Greg.

git add --intent-to-add bundled/
git diff --exit-code HEAD -- bundled/

- name: Vet the Go package
run: go vet ./...
27 changes: 27 additions & 0 deletions .github/workflows/zizmor.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
name: GitHub Actions Security Analysis with zizmor

on:
push:
branches: ["main"]
pull_request:
branches: ["**"]

permissions: {}

jobs:
zizmor:
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- name: Checkout repository
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false

- name: Run zizmor
uses: zizmorcore/zizmor-action@3dc1ecc9bcb9e94e9b2c709687979e1298497054 # v0.6.2
with:
# Report findings in the job log instead of uploading them to code
# scanning.
advanced-security: false

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sets advanced-security: false, so zizmor findings only go to the job log. dev-site and every other repo I checked (mmdbwriter, geoipupdate, GeoIP2-node, minfraud-api-node) omit this input and give the job security-events: write, so findings show in the code scanning tab.

Is there a reason to differ here? If not, suggestion: remove the advanced-security input and change the job permission from contents: read to security-events: write to match the other repos.

馃 Comment by Claude (Claude Code) on behalf of Will.

@oschwald oschwald Sep 24, 2026 •

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This repository is currently private with GitHub code security disabled, so SARIF/code-scanning integration is unavailable. Keeping advanced-security: false for now; the zizmor check still runs and reports findings in CI. We can align the integration when the repository is made public or code security is enabled.

馃 Response by Codex on behalf of Greg.

1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
node_modules/
23 changes: 23 additions & 0 deletions .precious.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
[commands.prettier]
type = "both"
include = ["**/*.{json,md,yaml,yml}"]
exclude = ["bundled/**", "pnpm-lock.yaml"]
cmd = ["pnpm", "exec", "prettier"]
invoke = "once"
path-args = "absolute-file"
lint-flags = ["--check"]
tidy-flags = ["--write"]
ok-exit-codes = 0
lint-failure-exit-codes = 1
ignore-stderr = ["Code style issues"]

[commands.redocly]
type = "lint"
include = ["specs/**", "components/**", "examples/**", "redocly.yaml"]
cmd = ["pnpm", "exec", "redocly", "lint"]
invoke = "once"
path-args = "none"
ok-exit-codes = 0
lint-failure-exit-codes = 1
# Redocly writes its progress to stderr. The exit code reports lint failures.
ignore-stderr = ["validated in"]
3 changes: 3 additions & 0 deletions .prettierrc.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
{
"proseWrap": "always"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This Prettier config only sets proseWrap. dev-site uses .prettierrc with singleQuote: true, trailingComma: "es5" and a Markdown override. As a result, the YAML in this repo uses double quotes, for example in dependabot.yml, while the same file in dev-site uses single quotes.

Do we want to match the dev-site config so shared files such as dependabot.yml and the workflows stay byte-identical across repos? If the difference is intended, that is fine, but it will make copying config between repos noisier.

馃 Comment by Claude (Claude Code) on behalf of Will.

@oschwald oschwald Sep 24, 2026 •

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving the current formatting configuration in this PR. Matching dev-site would be a separate formatting-only change; byte-identical shared configuration is not currently a requirement.

馃 Response by Codex on behalf of Greg.

}
7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Changelog

## 0.1.0

- Add the GeoIP and GeoLite web services spec.
- Add the minFraud web services spec.
- Add the Privacy Exclusions, License Key Validation, and download specs.
202 changes: 202 additions & 0 deletions LICENSE-APACHE
Original file line number Diff line number Diff line change
@@ -0,0 +1,202 @@

Apache License
Version 2.0, January 2004
https://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.

You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
17 changes: 17 additions & 0 deletions LICENSE-MIT
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do
so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Loading
Loading