Add attaching images from the post

.bundle/config

@@ -0,0 +1,2 @@
+---
+BUNDLE_PATH: "vendor/bundle"

.prettierrc.json

@@ -0,0 +1,5 @@
+{
+  "plugins": ["@prettier/plugin-ruby"],
+  "singleQuote": true,
+  "rubySingleQuote": true
+}

.rubocop.yml

@@ -0,0 +1,2 @@
+Style/StringLiterals:
+  EnforcedStyle: single_quotes

gems/3.3.2/gems/mime-types-3.5.1/.standard.yml

@@ -0,0 +1,4 @@
+parallel: true
+ruby_version: 2.3
+ignore:
+  - 'mime-types.gemspec'

gems/3.3.2/gems/mime-types-3.5.1/Code-of-Conduct.md

@@ -0,0 +1,73 @@
+# 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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 e-mail
+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 [INSERT EMAIL ADDRESS]. 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org

gems/3.3.2/gems/mime-types-3.5.1/Contributing.md

@@ -0,0 +1,132 @@
+# Contributing
+
+I value any contribution to mime-types you can provide: a bug report, a feature
+request, or code contributions.
+
+There are a few guidelines for contributing to mime-types:
+
+- Code changes _will_ _not_ be accepted without tests. The test suite is
+  written with [minitest][].
+- Match my coding style.
+- Use a thoughtfully-named topic branch that contains your change. Rebase your
+  commits into logical chunks as necessary.
+- Use [quality commit messages][].
+- Do not change the version number; when your patch is accepted and a release
+  is made, the version will be updated at that point.
+- Submit a GitHub pull request with your changes.
+- New or changed behaviours require new or updated documentation.
+
+## Adding or Modifying MIME Types
+
+The mime-types registry is no longer contained in mime-types, but in
+[mime-types-data][]. Please see that project for contributions there.
+
+### Test Dependencies
+
+mime-types uses Ryan Davis’s [Hoe][] to manage the release process, and it adds
+a number of rake tasks. You will mostly be interested in `rake`, which runs the
+tests the same way that `rake test` will do.
+
+To assist with the installation of the development dependencies for
+mime-types, I have provided the simplest possible Gemfile pointing to the
+(generated) `mime-types.gemspec` file. This will permit you to do `bundle install` to get the development dependencies. If you already have `hoe`
+installed, you can accomplish the same thing with `rake newb`.
+
+This task will install any missing dependencies, run the tests/specs, and
+generate the RDoc.
+
+You can run tests with code coverage analysis by running `rake test:coverage`.
+
+## Benchmarks
+
+mime-types offers several benchmark tasks to measure different measures of
+performance.
+
+There is a repeated load test, measuring how long it takes to start and load
+mime-types with its full registry. By default, it runs fifty loops and uses the
+built-in benchmark library:
+
+- `rake benchmark:load`
+
+There are two allocation tracing benchmarks (for normal and columnar loads).
+These can only be run on Ruby 2.1 or better and requires the
+[allocation\_tracer][] gem (not installed by default).
+
+- `rake benchmark:allocations`
+- `rake benchmark:allocations:columnar`
+
+There are two loaded object count benchmarks (for normal and columnar loads).
+These use `ObjectSpace.count_objects`.
+
+- `rake benchmark:objects`
+- `rake benchmark:objects:columnar`
+
+## Workflow
+
+Here's the most direct way to get your work merged into the project:
+
+- Fork the project.
+- Clone down your fork (`git clone git://github.com/<username>/ruby-mime-types.git`).
+- Create a topic branch to contain your change (`git checkout -b my_awesome_feature`).
+- Hack away, add tests. Not necessarily in that order.
+- Make sure everything still passes by running `rake`.
+- If necessary, rebase your commits into logical chunks, without errors.
+- Push the branch up (`git push origin my_awesome_feature`).
+- Create a pull request against mime-types/ruby-mime-types and describe what
+  your change does and the why you think it should be merged.
+
+## Contributors
+
+- Austin Ziegler created mime-types.
+
+Thanks to everyone else who has contributed to mime-types over the years:
+
+- Aaron Patterson
+- Alex Vondrak
+- Aggelos Avgerinos
+- Al Snow
+- Andre Pankratz
+- Andy Brody
+- Arnaud Meuret
+- Brandon Galbraith
+- Burke Libbey
+- Chris Gat
+- David Genord
+- Dillon Welch
+- Eric Marden
+- Edward Betts
+- Garret Alfert
+- Godfrey Chan
+- Greg Brockman
+- Hans de Graaff
+- Henrik Hodne
+- Igor Victor
+- Janko Marohnić
+- Jean Boussier
+- Jeremy Evans
+- Juanito Fatas
+- Jun Aruga
+- Łukasz Śliwa
+- Keerthi Siva
+- Ken Ip
+- Kevin Menard
+- Koichi ITO
+- Martin d'Allens
+- Mauricio Linhares
+- Nicolas Leger
+- Nicholas La Roux
+- nycvotes-dev
+- Olle Jonsson
+- Postmodern
+- Richard Hirner
+- Richard Hurt
+- Richard Schneeman
+- Robb Shecter
+- Tibor Szolár
+- Todd Carrico
+
+[minitest]: https://github.com/seattlerb/minitest
+[quality commit messages]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[mime-types-data]: https://github.com/mime-types/mime-types-data
+[hoe]: https://github.com/seattlerb/hoe
+[allocation\_tracer]: https://github.com/ko1/allocation_tracer