legion-json 1.2.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a311ed10affbc674c08cc97946b5085124a18eef12063a2251fc56ba1e0ab1ea
-  data.tar.gz: 19dec28ecc80573ef9869b78d2a8a51a886e32c1e71c12b82c69e547d59f5593
+  metadata.gz: 11ab7448be6e9b13f53af4616d69769eb6fc4dd83f816f5b9d2deb85bc0849a2
+  data.tar.gz: 0d27d2aaaa7fd763578f5d1ace8dbf844d4e0d5c85c91ebc6485b64c884406be
 SHA512:
-  metadata.gz: 9659cdb65d8c4e0a0ae1538f4719a8a646e4674debacf7b99cbb64afac3223dc69e731e05cdd32d54e3ee33f134bd4c294108080ea46c84d819d13794acfa3a2
-  data.tar.gz: 24bcb5e6dfe3bc7ed25f6aeaa35577d3ec57fc95eefe024dde6ce72986d6c00ec58181c191727de73321e85fcd7e3dafc04d7f57223ab3a16f8aab9d546721d4
+  metadata.gz: a0bd1762d708ec6c4bb7781fbbd77d2ce165b4d0f68e3a64d221d785751b622d8a6f681531d9461d92ca453e13be6d9d0571bad4008d0d4f83bc9d7e3f8e579a
+  data.tar.gz: 79a754a90f0fcc39efc1bfccf1d894019ae329d06aeb6ece45220a31498a9f02e3593ed72334817db198a06f932f32f78091716df9d656ea360cb56ab2e53303

data/.github/workflows/ci.yml

@@ -0,0 +1,16 @@
+name: CI
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  ci:
+    uses: LegionIO/.github/.github/workflows/ci.yml@main
+
+  release:
+    needs: ci
+    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+    uses: LegionIO/.github/.github/workflows/release.yml@main
+    secrets:
+      rubygems-api-key: ${{ secrets.RUBYGEMS_API_KEY }}

data/.rubocop.yml

@@ -1,22 +1,51 @@
+AllCops:
+  TargetRubyVersion: 3.4
+  NewCops: enable
+  SuggestExtensions: false
+
 Layout/LineLength:
-  Max: 120
-  Exclude:
-    - '*.gemspec'
+  Max: 160
+
+Layout/SpaceAroundEqualsInParameterDefault:
+  EnforcedStyle: space
+
+Layout/HashAlignment:
+  EnforcedHashRocketStyle: table
+  EnforcedColonStyle: table
+
 Metrics/MethodLength:
-  Max: 30
+  Max: 50
+
 Metrics/ClassLength:
   Max: 1500
+
+Metrics/ModuleLength:
+  Max: 1500
+
 Metrics/BlockLength:
-  Max: 50
-Style/OptionalBooleanParameter:
-  Enabled: false
+  Max: 40
+  AllowedPatterns: ['describe', 'context', 'it', 'shared_examples']
+  Exclude:
+    - 'spec/**/*'
+
+Metrics/AbcSize:
+  Max: 60
+
+Metrics/CyclomaticComplexity:
+  Max: 15
+
+Metrics/PerceivedComplexity:
+  Max: 17
+
 Style/Documentation:
   Enabled: false
-AllCops:
-  TargetRubyVersion: 2.5
-  NewCops: enable
-  SuggestExtensions: false
+
+Style/SymbolArray:
+  Enabled: true
+
 Style/FrozenStringLiteralComment:
+  Enabled: true
+  EnforcedStyle: always
+
+Naming/FileName:
   Enabled: false
-Gemspec/RequiredRubyVersion:
-  Enabled: false

data/.ruby-version

@@ -0,0 +1 @@
+3.4.8

data/CHANGELOG.md

@@ -1,4 +1,9 @@
 # Legion::JSON
 
+## [1.2.1] - 2026-03-22
+
+### Added
+- `Legion::JSON::Helper` mixin module with `json_load` and `json_dump` convenience methods for LEX extensions
+
 ## v1.2.0
-Moving from BitBucket to GitHub inside the Optum org. All git history is reset from this point on
+Moving from BitBucket to GitHub. All git history is reset from this point on

data/CLAUDE.md

@@ -0,0 +1,66 @@
+# legion-json: JSON Wrapper for LegionIO
+
+**Repository Level 3 Documentation**
+- **Parent**: `/Users/miverso2/rubymine/legion/CLAUDE.md`
+
+## Purpose
+
+JSON wrapper module for the LegionIO framework. Wraps `multi_json` and `json_pure` to provide a consistent JSON interface across all Legion gems and extensions. Automatically uses faster C-extension JSON gems (like `oj`) when available.
+
+**GitHub**: https://github.com/LegionIO/legion-json
+**Version**: 1.2.0
+**License**: Apache-2.0
+
+## Architecture
+
+```
+Legion::JSON
+├── .load(string, symbolize_keys: true)   # Deserialize JSON -> Hash
+├── .dump(object, pretty: false)          # Serialize Hash -> JSON
+├── InvalidJson                            # Custom error class
+└── ParseError                             # JSON parse error class
+```
+
+### Key Design Patterns
+
+- **Thin Wrapper**: Delegates to `MultiJson.load` / `MultiJson.dump`
+- **Symbolized Keys by Default**: `symbolize_keys: true` is the default (unlike standard JSON)
+- **Auto C-Extension**: If `oj` gem is installed, `multi_json` automatically uses it for performance
+
+## Dependencies
+
+| Gem | Purpose |
+|-----|---------|
+| `multi_json` | JSON adapter abstraction |
+| `json_pure` | Pure-Ruby JSON fallback |
+
+## File Map
+
+| Path | Purpose |
+|------|---------|
+| `lib/legion/json.rb` | Module entry with `load`/`dump` methods |
+| `lib/legion/json/invalid_json.rb` | InvalidJson error class |
+| `lib/legion/json/parse_error.rb` | ParseError class |
+| `lib/legion/json/version.rb` | VERSION constant |
+
+## Role in LegionIO
+
+**Foundation gem** - used by nearly every other Legion gem. `legion-settings` depends on it directly for config file parsing. All message serialization flows through this module.
+
+Note: Inside the `Legion::` namespace, `JSON` refers to `Legion::JSON` — callers outside this gem must use `::JSON` to access the stdlib.
+
+```
+legion-json
+  ^
+  |-- legion-settings
+  |     ^
+  |     |-- legion-cache
+  |     |-- legion-data
+  |     |-- legion-transport
+  |     └-- LegionIO
+  └-- legion-transport (direct dependency)
+```
+
+---
+
+**Maintained By**: Matthew Iverson (@Esity)

data/Gemfile

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 source 'https://rubygems.org'
 
 gemspec

data/LICENSE

@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright 2021 Optum
+   Copyright 2021 Esity
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

data/README.md

@@ -1,43 +1,40 @@
-Legion::Json
-=====
+# legion-json
 
-Legion::Json is the JSON wrapper that is used by the LegionIO framework. It gives all other gems and extensions a single 
-json library to use for consistency. It wraps [multi_json](https://rubygems.org/gems/multi_json) and also [json_pure](https://rubygems.org/gems/json_pure)
+JSON wrapper module for the [LegionIO](https://github.com/LegionIO/LegionIO) framework. Wraps `multi_json` and `json_pure` to provide a consistent JSON interface across all Legion gems and extensions. Automatically uses faster C-extension JSON gems (like `oj`) when available.
 
-Additional C extension style json gems can be installed like [oj](https://rubygems.org/gems/oj) and it they should be 
-used automatically. 
+**Version**: 1.2.0
 
-Supported Ruby versions and implementations
-------------------------------------------------
+## Installation
 
-Legion::Json should work identically on:
+```bash
+gem install legion-json
+```
 
- * JRuby 9.2+
- * Ruby 2.4+
+Or add to your Gemfile:
 
+```ruby
+gem 'legion-json'
+```
 
-Installation and Usage
-------------------------
+## Usage
 
-You can verify your installation using this piece of code:
+```ruby
+require 'legion/json'
 
-```bash
-gem install legion-json
+json_string = '{"foo":"bar","nested":{"hello":"world"}}'
+Legion::JSON.load(json_string)                          # => {foo: "bar", nested: {hello: "world"}}
+Legion::JSON.load(json_string, symbolize_keys: false)   # => {"foo" => "bar", ...}
+
+hash = { foo: 'bar', nested: { hello: 'world' } }
+Legion::JSON.dump(hash)                                 # => '{"foo":"bar","nested":{"hello":"world"}}'
 ```
 
-```ruby
-require 'legion-json'
-json_string = '{"foo":"bar","nested":{"hello":"world"}}'
-Legion::Json.load(json_string)
-Legion::Json.load(json_string, symbolize_keys: false) # symbolize_keys defaults to true
+Keys are symbolized by default, unlike standard Ruby JSON.
 
-hash = {foo: 'bar', nested: {hello: 'world'}}
-Legion::Json.dump(hash)
-Legion::Json.dump(hash, )
+## Requirements
 
-```
+- Ruby >= 3.4
 
-Authors
-----------
+## License
 
-* [Matthew Iverson](https://github.com/Esity) - current maintainer
+Apache-2.0

data/legion-json.gemspec

@@ -6,24 +6,24 @@ Gem::Specification.new do |spec|
   spec.name = 'legion-json'
   spec.version       = Legion::Json::VERSION
   spec.authors       = ['Esity']
-  spec.email         = %w[matthewdiverson@gmail.com ruby@optum.com]
+  spec.email         = ['matthewdiverson@gmail.com']
 
   spec.summary       = 'Wraps multi_json, json_pure and others to allow for interchanging json gems without deploying all new extensions'
   spec.description   = 'A JSON wrapper module for the LegionIO framework'
-  spec.homepage      = 'https://github.com/Optum/legion-json'
+  spec.homepage      = 'https://github.com/LegionIO/legion-json'
   spec.license       = 'Apache-2.0'
   spec.require_paths = ['lib']
-  spec.required_ruby_version = '>= 2.4'
+  spec.required_ruby_version = '>= 3.4'
   spec.files = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
-  spec.test_files        = spec.files.select { |p| p =~ %r{^test/.*_test.rb} }
-  spec.extra_rdoc_files  = %w[README.md LICENSE CHANGELOG.md]
+  spec.extra_rdoc_files = %w[README.md LICENSE CHANGELOG.md]
   spec.metadata = {
-    'bug_tracker_uri' => 'https://github.com/Optum/legion-json/issues',
-    'changelog_uri' => 'https://github.com/Optum/legion-json/src/main/CHANGELOG.md',
-    'documentation_uri' => 'https://github.com/Optum/legion-json',
-    'homepage_uri' => 'https://github.com/Optum/LegionIO',
-    'source_code_uri' => 'https://github.com/Optum/legion-json',
-    'wiki_uri' => 'https://github.com/Optum/legion-json/wiki'
+    'bug_tracker_uri'       => 'https://github.com/LegionIO/legion-json/issues',
+    'changelog_uri'         => 'https://github.com/LegionIO/legion-json/blob/main/CHANGELOG.md',
+    'documentation_uri'     => 'https://github.com/LegionIO/legion-json',
+    'homepage_uri'          => 'https://github.com/LegionIO/LegionIO',
+    'source_code_uri'       => 'https://github.com/LegionIO/legion-json',
+    'wiki_uri'              => 'https://github.com/LegionIO/legion-json/wiki',
+    'rubygems_mfa_required' => 'true'
   }
 
   spec.add_dependency 'json_pure'

data/lib/legion/json/helper.rb

@@ -0,0 +1,15 @@
+# frozen_string_literal: true
+
+module Legion
+  module JSON
+    module Helper
+      def json_load(string, symbolize_keys: true)
+        Legion::JSON.load(string, symbolize_keys: symbolize_keys)
+      end
+
+      def json_dump(object, pretty: false)
+        Legion::JSON.dump(object, pretty: pretty)
+      end
+    end
+  end
+end

data/lib/legion/json/invalid_json.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 module Legion
   module Exception
     class InvalidJson < StandardError; end

data/lib/legion/json/parse_error.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 module Legion
   module JSON
     # The Legion JSON parser error abstraction.

data/lib/legion/json/version.rb

@@ -1,5 +1,7 @@
+# frozen_string_literal: true
+
 module Legion
   module Json
-    VERSION = '1.2.0'.freeze
+    VERSION = '1.2.1'
   end
 end

data/lib/legion/json.rb

@@ -1,8 +1,11 @@
+# frozen_string_literal: true
+
 require 'legion/json/version'
 require 'legion/json/parse_error'
 require 'legion/json/invalid_json'
 require 'json'
 require 'multi_json'
+require_relative 'json/helper'
 
 module Legion
   module JSON

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: legion-json
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.2.1
 platform: ruby
 authors:
 - Esity
-autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-06-04 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: json_pure
@@ -41,45 +40,40 @@ dependencies:
 description: A JSON wrapper module for the LegionIO framework
 email:
 - matthewdiverson@gmail.com
-- ruby@optum.com
 executables: []
 extensions: []
 extra_rdoc_files:
-- README.md
-- LICENSE
 - CHANGELOG.md
+- LICENSE
+- README.md
 files:
-- ".github/workflows/sourcehawk-scan.yml"
+- ".github/workflows/ci.yml"
 - ".gitignore"
 - ".rubocop.yml"
+- ".ruby-version"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
-- CONTRIBUTING.md
+- CLAUDE.md
 - Gemfile
-- INDIVIDUAL_CONTRIBUTOR_LICENSE.md
 - LICENSE
-- NOTICE.txt
 - README.md
-- SECURITY.md
-- attribution.txt
 - legion-json.gemspec
 - lib/legion/json.rb
+- lib/legion/json/helper.rb
 - lib/legion/json/invalid_json.rb
 - lib/legion/json/parse_error.rb
 - lib/legion/json/version.rb
 - sonar-project.properties
-- sourcehawk.yml
-homepage: https://github.com/Optum/legion-json
+homepage: https://github.com/LegionIO/legion-json
 licenses:
 - Apache-2.0
 metadata:
-  bug_tracker_uri: https://github.com/Optum/legion-json/issues
-  changelog_uri: https://github.com/Optum/legion-json/src/main/CHANGELOG.md
-  documentation_uri: https://github.com/Optum/legion-json
-  homepage_uri: https://github.com/Optum/LegionIO
-  source_code_uri: https://github.com/Optum/legion-json
-  wiki_uri: https://github.com/Optum/legion-json/wiki
-post_install_message:
+  bug_tracker_uri: https://github.com/LegionIO/legion-json/issues
+  changelog_uri: https://github.com/LegionIO/legion-json/blob/main/CHANGELOG.md
+  documentation_uri: https://github.com/LegionIO/legion-json
+  homepage_uri: https://github.com/LegionIO/LegionIO
+  source_code_uri: https://github.com/LegionIO/legion-json
+  wiki_uri: https://github.com/LegionIO/legion-json/wiki
+  rubygems_mfa_required: 'true'
 rdoc_options: []
 require_paths:
 - lib
@@ -87,15 +81,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '2.4'
+      version: '3.4'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.6
-signing_key:
+rubygems_version: 3.6.9
 specification_version: 4
 summary: Wraps multi_json, json_pure and others to allow for interchanging json gems
   without deploying all new extensions

data/.github/workflows/sourcehawk-scan.yml

@@ -1,20 +0,0 @@
-name: Sourcehawk Scan
-on:
-  push:
-    branches:
-      - main
-      - master
-  pull_request:
-    branches:
-      - main
-      - master
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-      - name: Sourcehawk Scan
-        uses: optum/sourcehawk-scan-github-action@main
-
-
-

data/CODE_OF_CONDUCT.md

@@ -1,75 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project email
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [opensource@optum.com][email]. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
-[email]: mailto:opensource@optum.com

data/CONTRIBUTING.md

@@ -1,55 +0,0 @@
-# Contribution Guidelines
-
-Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. Please also review our [Contributor License Agreement ("CLA")](INDIVIDUAL_CONTRIBUTOR_LICENSE.md) prior to submitting changes to the project.  You will need to attest to this agreement following the instructions in the [Paperwork for Pull Requests](#paperwork-for-pull-requests) section below.
-
----
-
-# How to Contribute
-
-Now that we have the disclaimer out of the way, let's get into how you can be a part of our project. There are many different ways to contribute.
-
-## Issues
-
-We track our work using Issues in GitHub. Feel free to open up your own issue to point out areas for improvement or to suggest your own new experiment. If you are comfortable with signing the waiver linked above and contributing code or documentation, grab your own issue and start working.
-
-## Coding Standards
-
-We have some general guidelines towards contributing to this project.
-Please run RSpec and Rubocop while developing code for LegionIO
-
-### Languages
-
-*Ruby*
-
-## Pull Requests
-
-If you've gotten as far as reading this section, then thank you for your suggestions.
-
-## Paperwork for Pull Requests
-
-* Please read this guide and make sure you agree with our [Contributor License Agreement ("CLA")](INDIVIDUAL_CONTRIBUTOR_LICENSE.md).
-* Make sure git knows your name and email address:
-   ```
-   $ git config user.name "J. Random User"
-   $ git config user.email "j.random.user@example.com"
-   ```
->The name and email address must be valid as we cannot accept anonymous contributions.
-* Write good commit messages.
-> Concise commit messages that describe your changes help us better understand your contributions.
-* The first time you open a pull request in this repository, you will see a comment on your PR with a link that will allow you to sign our Contributor License Agreement (CLA) if necessary.
-> The link will take you to a page that allows you to view our CLA.  You will need to click the `Sign in with GitHub to agree button` and authorize the cla-assistant application to access the email addresses associated with your GitHub account.  Agreeing to the CLA is also considered to be an attestation that you either wrote or have the rights to contribute the code.  All committers to the PR branch will be required to sign the CLA, but you will only need to sign once.  This CLA applies to all repositories in the Optum org.
-
-## General Guidelines
-
-Ensure your pull request (PR) adheres to the following guidelines:
-
-* Try to make the name concise and descriptive.
-* Give a good description of the change being made. Since this is very subjective, see the [Updating Your Pull Request (PR)](#updating-your-pull-request-pr) section below for further details.
-* Every pull request should be associated with one or more issues. If no issue exists yet, please create your own.
-* Make sure that all applicable issues are mentioned somewhere in the PR description. This can be done by typing # to bring up a list of issues.
-
-### Updating Your Pull Request (PR)
-
-A lot of times, making a PR adhere to the standards above can be difficult. If the maintainers notice anything that we'd like changed, we'll ask you to edit your PR before we merge it. This applies to both the content documented in the PR and the changed contained within the branch being merged. There's no need to open a new PR. Just edit the existing one.
-
-[email]: mailto:opensource@optum.com

data/INDIVIDUAL_CONTRIBUTOR_LICENSE.md

@@ -1,30 +0,0 @@
-# Individual Contributor License Agreement ("Agreement") V2.0
-
-Thank you for your interest in this Optum project (the "PROJECT"). In order to clarify the intellectual property license granted with Contributions from any person or entity, the PROJECT must have a Contributor License Agreement ("CLA") on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for your protection as a Contributor as well as the protection of the PROJECT and its users; it does not change your rights to use your own Contributions for any other purpose.
-
-You accept and agree to the following terms and conditions for Your present and future Contributions submitted to the PROJECT. In return, the PROJECT shall not use Your Contributions in a way that is inconsistent with stated project goals in effect at the time of the Contribution. Except for the license granted herein to the PROJECT and recipients of software distributed by the PROJECT, You reserve all right, title, and interest in and to Your Contributions.
-1.	Definitions.
-
-"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with the PROJECT. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. 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.
-
-"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to the PROJECT for inclusion in, or documentation of, any of the products owned or managed by the PROJECT (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the PROJECT 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 PROJECT for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
-
-2.	Grant of Copyright License.
-
-Subject to the terms and conditions of this Agreement, You hereby grant to the PROJECT and to recipients of software distributed by the PROJECT 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 Your Contributions and such derivative works.
-
-3.	Grant of Patent License.
-
-Subject to the terms and conditions of this Agreement, You hereby grant to the PROJECT and to recipients of software distributed by the PROJECT 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 You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.
-
-4.	Representations.
-
-    (a)	You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to the PROJECT, or that your employer has executed a separate Corporate CLA with the PROJECT.
-
-    (b)	You represent that each of Your Contributions is Your original creation (see section 6 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.
-
-5.   You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your 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.
-
-6.  Should You wish to submit work that is not Your original creation, You may submit it to the PROJECT separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".
-
-7.  You agree to notify the PROJECT of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect. 

data/NOTICE.txt

@@ -1,9 +0,0 @@
-Legion::Json(legion-json)
-Copyright 2021 Optum
-
-Project Description:
-====================
-A JSON wrapper module for the LegionIO framework
-
-Author(s):
-Esity

data/SECURITY.md

@@ -1,9 +0,0 @@
-# Security Policy
-
-## Supported Versions
-| Version | Supported          |
-| ------- | ------------------ |
-| 1.x.x   | :white_check_mark: |
-
-## Reporting a Vulnerability
-To be added

data/attribution.txt

@@ -1 +0,0 @@
-Add attributions here.

data/sourcehawk.yml

@@ -1,4 +0,0 @@
-
-config-locations:
-  - https://raw.githubusercontent.com/optum/.github/main/sourcehawk.yml
-