png_conform 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: f04021d7929787c975ea7a73dd7265754a6e33ed54bf27ecd85221dd820104c9
+  data.tar.gz: 4435b4bbb7419ab1f94e37210f19a3ba9fb8fb929578aa56dc28b2cc9b5782e9
+SHA512:
+  metadata.gz: bf874e6d45f148881ee330c67be8f0ec835ad6b7c0effc7406ae4e1e1c8ad2e6973f065a28fad08c46cb334c64614cf81419f4b228ade34739bfaff792143f42
+  data.tar.gz: 59f6957a6629e0b88c3a1a6b2a2e7950cdac2c851fa37748d3ddb781d6a74ef898a9da0f5b2195373433a2b5f6c32825c7a5ca5b9e3a92813cd77cef3df7dc5b

data/.rspec

@@ -0,0 +1,3 @@
+--require spec_helper
+--color
+--format documentation

data/.rubocop.yml

@@ -0,0 +1,19 @@
+# Auto-generated by Cimas: Do not edit it manually!
+# See https://github.com/metanorma/cimas
+inherit_from:
+  - https://raw.githubusercontent.com/riboseinc/oss-guides/main/ci/rubocop.yml
+  - .rubocop_todo.yml
+
+inherit_mode:
+  merge:
+    - Exclude
+
+# local repo-specific modifications
+# ...
+plugins:
+  - rubocop-rspec
+  - rubocop-performance
+  - rubocop-rake
+
+AllCops:
+  TargetRubyVersion: 3.0

data/.rubocop_todo.yml

@@ -0,0 +1,197 @@
+# This configuration was generated by
+# `rubocop --auto-gen-config`
+# on 2025-11-17 11:51:04 UTC using RuboCop version 1.81.1.
+# The point is for the user to remove these configuration records
+# one by one as the offenses are removed from the code base.
+# Note that changes in the inspected code, or installation of new
+# versions of RuboCop, may require this file to be generated again.
+
+# Offense count: 1
+# This cop supports safe autocorrection (--autocorrect).
+# Configuration parameters: IndentationWidth.
+Layout/AssignmentIndentation:
+  Exclude:
+    - 'lib/png_conform/models/file_analysis.rb'
+
+# Offense count: 2
+# This cop supports safe autocorrection (--autocorrect).
+# Configuration parameters: EnforcedStyleAlignWith.
+# SupportedStylesAlignWith: either, start_of_block, start_of_line
+Layout/BlockAlignment:
+  Exclude:
+    - 'lib/png_conform/models/file_analysis.rb'
+    - 'lib/png_conform/services/validation_service.rb'
+
+# Offense count: 2
+# This cop supports safe autocorrection (--autocorrect).
+Layout/BlockEndNewline:
+  Exclude:
+    - 'lib/png_conform/models/file_analysis.rb'
+    - 'lib/png_conform/services/validation_service.rb'
+
+# Offense count: 4
+# This cop supports safe autocorrection (--autocorrect).
+# Configuration parameters: Width, AllowedPatterns.
+Layout/IndentationWidth:
+  Exclude:
+    - 'lib/png_conform/models/file_analysis.rb'
+    - 'lib/png_conform/services/validation_service.rb'
+
+# Offense count: 194
+# This cop supports safe autocorrection (--autocorrect).
+# Configuration parameters: Max, AllowHeredoc, AllowURI, AllowQualifiedName, URISchemes, IgnoreCopDirectives, AllowedPatterns, SplitStrings.
+# URISchemes: http, https
+Layout/LineLength:
+  Enabled: false
+
+# Offense count: 1
+# This cop supports safe autocorrection (--autocorrect).
+# Configuration parameters: AllowInHeredoc.
+Layout/TrailingWhitespace:
+  Exclude:
+    - 'lib/png_conform/models/file_analysis.rb'
+
+# Offense count: 1
+Lint/BinaryOperatorWithIdenticalOperands:
+  Exclude:
+    - 'lib/png_conform/validators/ancillary/itxt_validator.rb'
+
+# Offense count: 7
+# Configuration parameters: IgnoreLiteralBranches, IgnoreConstantBranches, IgnoreDuplicateElseBranch.
+Lint/DuplicateBranch:
+  Exclude:
+    - 'lib/png_conform/reporters/reporter_factory.rb'
+    - 'lib/png_conform/services/zlib_validator.rb'
+    - 'lib/png_conform/validators/ancillary/sbit_validator.rb'
+    - 'spec/pngsuite/helpers/semantic_validator.rb'
+
+# Offense count: 1
+# This cop supports safe autocorrection (--autocorrect).
+Lint/UselessAssignment:
+  Exclude:
+    - 'examples/advanced_usage.rb'
+
+# Offense count: 99
+# Configuration parameters: AllowedMethods, AllowedPatterns, CountRepeatedAttributes, Max.
+Metrics/AbcSize:
+  Enabled: false
+
+# Offense count: 2
+# Configuration parameters: CountComments, CountAsOne, AllowedMethods, AllowedPatterns, inherit_mode.
+# AllowedMethods: refine
+Metrics/BlockLength:
+  Max: 52
+
+# Offense count: 55
+# Configuration parameters: AllowedMethods, AllowedPatterns, Max.
+Metrics/CyclomaticComplexity:
+  Enabled: false
+
+# Offense count: 146
+# Configuration parameters: CountComments, CountAsOne, AllowedMethods, AllowedPatterns.
+Metrics/MethodLength:
+  Max: 66
+
+# Offense count: 3
+# Configuration parameters: CountKeywordArgs, MaxOptionalParameters.
+Metrics/ParameterLists:
+  Max: 10
+
+# Offense count: 42
+# Configuration parameters: AllowedMethods, AllowedPatterns, Max.
+Metrics/PerceivedComplexity:
+  Enabled: false
+
+# Offense count: 1
+# Configuration parameters: EnforcedStyle, CheckMethodNames, CheckSymbols, AllowedIdentifiers, AllowedPatterns.
+# SupportedStyles: snake_case, normalcase, non_integer
+# AllowedIdentifiers: TLS1_1, TLS1_2, capture3, iso8601, rfc1123_date, rfc822, rfc2822, rfc3339, x86_64
+Naming/VariableNumber:
+  Exclude:
+    - 'lib/png_conform/validators/critical/plte_validator.rb'
+
+# Offense count: 10
+# Configuration parameters: MinSize.
+Performance/CollectionLiteralInLoop:
+  Exclude:
+    - 'examples/advanced_usage.rb'
+    - 'lib/png_conform/validators/chunk_registry.rb'
+
+# Offense count: 68
+# Configuration parameters: Prefixes, AllowedPatterns.
+# Prefixes: when, with, without
+RSpec/ContextWording:
+  Enabled: false
+
+# Offense count: 19
+# Configuration parameters: IgnoredMetadata.
+RSpec/DescribeClass:
+  Enabled: false
+
+# Offense count: 294
+# Configuration parameters: CountAsOne.
+RSpec/ExampleLength:
+  Max: 19
+
+# Offense count: 1
+RSpec/MultipleDescribes:
+  Exclude:
+    - 'spec/png_conform/validators/base_validator_spec.rb'
+
+# Offense count: 363
+RSpec/MultipleExpectations:
+  Max: 10
+
+# Offense count: 1
+# Configuration parameters: AllowSubject.
+RSpec/MultipleMemoizedHelpers:
+  Max: 6
+
+# Offense count: 2
+# Configuration parameters: CustomTransform, IgnoreMethods, IgnoreMetadata.
+RSpec/SpecFilePathFormat:
+  Exclude:
+    - 'spec/png_conform/bindata/chunk_structure_spec.rb'
+    - 'spec/png_conform/bindata/png_file_spec.rb'
+
+# Offense count: 45
+# Configuration parameters: IgnoreNameless, IgnoreSymbolicNames.
+RSpec/VerifiedDoubles:
+  Enabled: false
+
+# Offense count: 2
+# This cop supports safe autocorrection (--autocorrect).
+# Configuration parameters: EnforcedStyle, ProceduralMethods, FunctionalMethods, AllowedMethods, AllowedPatterns, AllowBracesOnProceduralOneLiners, BracesRequiredMethods.
+# SupportedStyles: line_count_based, semantic, braces_for_chaining, always_braces
+# ProceduralMethods: benchmark, bm, bmbm, create, each_with_object, measure, new, realtime, tap, with_object
+# FunctionalMethods: let, let!, subject, watch
+# AllowedMethods: lambda, proc, it
+Style/BlockDelimiters:
+  Exclude:
+    - 'lib/png_conform/models/file_analysis.rb'
+    - 'lib/png_conform/services/validation_service.rb'
+
+# Offense count: 31
+# This cop supports safe autocorrection (--autocorrect).
+# Configuration parameters: MaxUnannotatedPlaceholdersAllowed, Mode, AllowedMethods, AllowedPatterns.
+# SupportedStyles: annotated, template, unannotated
+Style/FormatStringToken:
+  EnforcedStyle: unannotated
+
+# Offense count: 1
+Style/MissingRespondToMissing:
+  Exclude:
+    - 'lib/png_conform/cli.rb'
+
+# Offense count: 1
+# This cop supports safe autocorrection (--autocorrect).
+Style/MultilineIfModifier:
+  Exclude:
+    - 'lib/png_conform/models/file_analysis.rb'
+
+# Offense count: 2
+# This cop supports unsafe autocorrection (--autocorrect-all).
+Style/SlicingWithRange:
+  Exclude:
+    - 'examples/advanced_usage.rb'
+    - 'examples/basic_usage.rb'

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at ronald.tse@ribose.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/CONTRIBUTING.md

@@ -0,0 +1,323 @@
+# Contributing to PngConform
+
+Thank you for your interest in contributing to PngConform! This document provides guidelines and instructions for contributing to the project.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Getting Started](#getting-started)
+- [Development Setup](#development-setup)
+- [Making Changes](#making-changes)
+- [Testing](#testing)
+- [Code Style](#code-style)
+- [Submitting Changes](#submitting-changes)
+- [Reporting Issues](#reporting-issues)
+
+## Code of Conduct
+
+This project adheres to the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+## Getting Started
+
+1. Fork the repository on GitHub
+2. Clone your fork locally
+3. Set up your development environment
+4. Create a topic branch for your changes
+5. Make your changes
+6. Test your changes
+7. Submit a pull request
+
+## Development Setup
+
+### Prerequisites
+
+- Ruby 3.0 or higher
+- Bundler gem
+
+### Setup Steps
+
+```bash
+# Clone your fork
+git clone https://github.com/YOUR_USERNAME/png_conform.git
+cd png_conform
+
+# Install dependencies
+bundle install
+
+# Run tests to verify setup
+bundle exec rake spec
+
+# Run linter
+bundle exec rubocop
+```
+
+## Making Changes
+
+### Architecture Principles
+
+PngConform follows strict architectural principles:
+
+1. **Object-Oriented Design**: Use proper encapsulation, inheritance, and polymorphism
+2. **MECE (Mutually Exclusive, Collectively Exhaustive)**: Each component should have exactly one responsibility
+3. **Separation of Concerns**: Maintain clear boundaries between layers
+4. **Model-Driven**: Prioritize model-to-model interaction over procedural code
+
+### Directory Structure
+
+```
+lib/png_conform/
+├── bindata/           # Binary parsing structures (BinData)
+├── models/            # Domain models (Lutaml::Model)
+├── validators/        # Validation logic
+│   ├── critical/      # PNG critical chunks
+│   ├── ancillary/     # PNG ancillary chunks
+│   ├── apng/          # APNG chunks
+│   ├── mng/           # MNG chunks
+│   └── jng/           # JNG chunks
+├── services/          # Orchestration and business logic
+├── readers/           # File reading strategies
+├── reporters/         # Output formatting
+└── commands/          # CLI commands
+```
+
+### Adding a New Chunk Validator
+
+1. Create the validator class in the appropriate directory:
+   ```ruby
+   # lib/png_conform/validators/ancillary/example_validator.rb
+   module PngConform
+     module Validators
+       module Ancillary
+         class ExampleValidator < BaseValidator
+           def validate
+             # Validation logic here
+             check_length(expected_length)
+             check_crc
+             # Add errors/warnings/info as needed
+           end
+         end
+       end
+     end
+   end
+   ```
+
+2. Register the validator in `lib/png_conform/validators/chunk_registry.rb`:
+   ```ruby
+   register("eXmP", Ancillary::ExampleValidator)
+   ```
+
+3. Add the require statement in `lib/png_conform.rb`:
+   ```ruby
+   require_relative "png_conform/validators/ancillary/example_validator"
+   ```
+
+4. Write comprehensive tests in `spec/png_conform/validators/ancillary/example_validator_spec.rb`
+
+### Adding a New Validation Profile
+
+1. Add profile definition in `lib/png_conform/services/profile_manager.rb`:
+   ```ruby
+   def example_profile
+     Profile.new(
+       name: "example",
+       description: "Example profile for specific use case",
+       required_chunks: %w[IHDR IDAT IEND],
+       optional_chunks: %w[...],
+       prohibited_chunks: %w[...]
+     )
+   end
+   ```
+
+2. Update documentation in `README.adoc`
+
+3. Add tests for the new profile
+
+## Testing
+
+### Running Tests
+
+```bash
+# Run all tests
+bundle exec rake spec
+
+# Run specific test file
+bundle exec rspec spec/path/to/spec_file.rb
+
+# Run tests with coverage (if configured)
+COVERAGE=true bundle exec rake spec
+```
+
+### Writing Tests
+
+Follow these principles:
+
+1. **One Test, One Behavior**: Each test should validate exactly one behavior
+2. **Descriptive Names**: Use clear, descriptive test names
+3. **Arrange-Act-Assert**: Structure tests with clear setup, execution, and assertion phases
+4. **Use Doubles**: Prefer test doubles over real objects for isolation
+5. **No Mocks for Models**: Don't mock domain model classes
+
+Example test structure:
+
+```ruby
+RSpec.describe PngConform::Validators::Ancillary::ExampleValidator do
+  describe "#validate" do
+    let(:chunk) { create_chunk("eXmP", data) }
+    let(:context) { PngConform::Validators::ValidationContext.new }
+    subject(:validator) { described_class.new(chunk, context) }
+
+    context "with valid data" do
+      let(:data) { "\x00\x01\x02\x03" }
+
+      it "does not add errors" do
+        validator.validate
+        expect(context.errors).to be_empty
+      end
+    end
+
+    context "with invalid length" do
+      let(:data) { "\x00\x01" }
+
+      it "adds length error" do
+        validator.validate
+        expect(context.errors).to include(
+          hash_including(message: /invalid length/)
+        )
+      end
+    end
+  end
+end
+```
+
+### Test Coverage Requirements
+
+- All new code must have corresponding tests
+- Aim for 100% coverage of new functionality
+- Tests must pass on all supported Ruby versions (3.0, 3.1, 3.2, 3.3)
+
+## Code Style
+
+### RuboCop
+
+All code must pass RuboCop checks:
+
+```bash
+bundle exec rubocop
+
+# Auto-fix issues where possible
+bundle exec rubocop -A
+```
+
+### Ruby Style Guidelines
+
+1. **Frozen String Literals**: Always use `# frozen_string_literal: true`
+2. **Line Length**: Maximum 80 characters (exceptions allowed for readability)
+3. **Method Length**: Keep methods focused and under 50 lines
+4. **Class Length**: Keep classes under 700 lines (refactor if larger)
+5. **No Hardcoding**: Use constants, configuration, or model properties
+
+### Documentation
+
+1. Use YARD-style comments for public APIs
+2. Include examples in documentation
+3. Update README.adoc for user-facing features
+4. Update ARCHITECTURE.md for design changes
+
+## Submitting Changes
+
+### Pull Request Process
+
+1. **Update Documentation**: Ensure README, CHANGELOG, and inline docs are updated
+2. **Write Tests**: All new features must have comprehensive tests
+3. **Run Quality Checks**:
+   ```bash
+   bundle exec rake spec    # All tests must pass
+   bundle exec rubocop      # 0 offenses required
+   ```
+
+4. **Commit Messages**: Use semantic commit messages:
+   ```
+   feat(validators): add support for eXmP chunk
+   fix(cli): correct argument parsing for --profile option
+   docs(readme): update installation instructions
+   test(validators): add tests for edge cases
+   refactor(models): extract common validation logic
+   chore(deps): update bindata to 2.5.1
+   ```
+
+5. **Create Pull Request**:
+   - Provide clear description of changes
+   - Reference any related issues
+   - Include screenshots for UI changes
+   - Ensure CI passes
+
+### Pull Request Template
+
+```markdown
+## Description
+Brief description of changes
+
+## Motivation and Context
+Why is this change required? What problem does it solve?
+
+## Type of Change
+- [ ] Bug fix (non-breaking change fixing an issue)
+- [ ] New feature (non-breaking change adding functionality)
+- [ ] Breaking change (fix or feature causing existing functionality to change)
+- [ ] Documentation update
+
+## How Has This Been Tested?
+Describe tests added or methodology used
+
+## Checklist
+- [ ] Code follows project style guidelines
+- [ ] Self-review of code completed
+- [ ] Code comments added where needed
+- [ ] Documentation updated
+- [ ] Tests added/updated
+- [ ] All tests pass
+- [ ] RuboCop passes with 0 offenses
+- [ ] CHANGELOG.md updated
+```
+
+## Reporting Issues
+
+### Bug Reports
+
+When reporting bugs, please include:
+
+1. **Ruby Version**: Output of `ruby -v`
+2. **Gem Version**: Output of `png_conform version`
+3. **Operating System**: OS and version
+4. **Steps to Reproduce**: Minimal example to reproduce the issue
+5. **Expected Behavior**: What you expected to happen
+6. **Actual Behavior**: What actually happened
+7. **Additional Context**: Any other relevant information
+
+### Feature Requests
+
+When requesting features, please include:
+
+1. **Use Case**: Describe the problem this feature would solve
+2. **Proposed Solution**: How you envision this feature working
+3. **Alternatives**: Other approaches you've considered
+4. **Additional Context**: Any other relevant information
+
+## Development Resources
+
+- [PNG Specification](https://www.w3.org/TR/PNG/)
+- [MNG Specification](http://www.libpng.org/pub/mng/spec/)
+- [APNG Specification](https://wiki.mozilla.org/APNG_Specification)
+- [BinData Documentation](https://github.com/dmendel/bindata/wiki)
+- [Lutaml Model Documentation](https://github.com/lutaml/lutaml-model)
+- [Thor Documentation](http://whatisthor.com/)
+
+## Questions?
+
+If you have questions about contributing, please:
+
+1. Check existing documentation (README, ARCHITECTURE)
+2. Search existing issues and pull requests
+3. Open a new issue with the "question" label
+
+Thank you for contributing to PngConform!

data/Gemfile

@@ -0,0 +1,13 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in png_conform.gemspec
+gemspec
+
+gem "rake"
+gem "rspec"
+gem "rubocop"
+gem "rubocop-performance"
+gem "rubocop-rake"
+gem "rubocop-rspec"

data/LICENSE

@@ -0,0 +1,43 @@
+BSD 2-Clause License
+
+Copyright (c) 2025, Ribose Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+---
+
+This project is a Ruby port of pngcheck, which is:
+
+   Copyright 1995-2020 by Alexander Lehmann <lehmann@usa.net>,
+                          Andreas Dilger <adilger@enel.ucalgary.ca>,
+                          Glenn Randers-Pehrson <randeg@alum.rpi.edu>,
+                          Greg Roelofs <newt@pobox.com>,
+                          John Bowler <jbowler@acm.org>,
+                          Tom Lane <tgl@sss.pgh.pa.us>
+
+   Permission to use, copy, modify, and distribute this software and its
+   documentation for any purpose and without fee is hereby granted, provided
+   that the above copyright notice appear in all copies and that both that
+   copyright notice and this permission notice appear in supporting
+   documentation.  This software is provided "as is" without express or
+   implied warranty.