Search Options

Results per page
Sort
Preferred Languages
Advance

Results 81 - 90 of 1,046 for included (0.07 sec)

  1. LICENSES/vendor/github.com/coredns/caddy/LICENSE

          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.
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Sun Jun 13 05:06:37 UTC 2021
    - 11.2K bytes
    - Viewed (0)
  2. LICENSES/vendor/github.com/coredns/corefile-migration/LICENSE

          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.
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  3. LICENSES/vendor/github.com/coreos/go-oidc/LICENSE

          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.
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  4. LICENSES/vendor/github.com/distribution/reference/LICENSE

          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.
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri Sep 01 01:53:40 UTC 2023
    - 11.2K bytes
    - Viewed (0)
  5. LICENSES/vendor/github.com/go-logr/logr/LICENSE

          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.
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Sat May 16 11:52:51 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  6. LICENSE

          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.
    
    Registered: Fri Sep 05 12:43:10 UTC 2025
    - Last Modified: Wed Feb 22 18:59:39 UTC 2023
    - 11.1K bytes
    - Viewed (0)
  7. LICENSES/third_party/forked/vishhstress/LICENSE

    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,
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Tue Feb 13 14:21:05 UTC 2024
    - 1K bytes
    - Viewed (0)
  8. LICENSES/vendor/github.com/Microsoft/hnslib/LICENSE

    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,
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Mon Oct 14 17:44:30 UTC 2024
    - 1.2K bytes
    - Viewed (0)
  9. LICENSE

          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.
    
    Registered: Thu Sep 04 12:52:25 UTC 2025
    - Last Modified: Tue May 08 21:35:34 UTC 2018
    - 11.1K bytes
    - Viewed (0)
  10. LICENSES/vendor/github.com/euank/go-kmsg-parser/LICENSE

          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.
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
Back to top