- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 167 for syntax (0.17 sec)
-
licenses/github.com/cncf/xds/go/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Thu Apr 15 19:34:51 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/coreos/go-oidc/v3/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Mon Oct 25 16:29:29 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/envoyproxy/go-control-plane/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Sat Oct 26 02:47:39 GMT 2019 - 11.1K bytes - Viewed (0) -
licenses/cloud.google.com/go/security/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Fri Aug 27 16:21:28 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/go-jose/go-jose/v4/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Mon Apr 08 17:05:56 GMT 2024 - 11.1K bytes - Viewed (0) -
licenses/cel.dev/expr/proto/test/v1/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Mon Apr 08 17:05:56 GMT 2024 - 11.1K bytes - Viewed (0) -
licenses/github.com/googleapis/enterprise-certificate-proxy/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Sat Jun 25 18:26:36 GMT 2022 - 11.1K bytes - Viewed (0) -
licenses/github.com/howardjohn/unshare-go/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Wed Jan 31 07:51:36 GMT 2024 - 11.1K bytes - Viewed (0) -
licenses/github.com/klauspost/compress/gzhttp/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Fri Aug 06 23:19:43 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/modern-go/concurrent/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.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Sat Oct 26 02:47:39 GMT 2019 - 11.1K bytes - Viewed (0)