Parents (Total: 5)

The searched file hash is included in 5 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	8910DBC0E22C2A475B42B67D8148492B
PackageArch	noarch
PackageDescription	General-purpose OAuth 1.0 authentication strategy for Passport. This module lets you authenticate using OAuth in your Node.js applications. By plugging into Passport, OAuth authentication can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express. Note that this strategy provides generic OAuth support. In many cases, a provider-specific strategy can be used instead, which cuts down on unnecessary configuration, and accommodates any provider-specific quirks. See the list for supported providers. Developers who need to implement authentication against an OAuth provider that is not already supported are encouraged to sub-class this strategy. If you choose to open source the new provider-specific strategy, please add it to the list so other people can find it.
PackageMaintainer	Fedora Project
PackageName	nodejs-passport-oauth1
PackageRelease	8.fc32
PackageVersion	1.1.0
SHA-1	092289412AAE6C48F26A57DB3606E58740106481
SHA-256	76DCDDCDAA8001476EB93FEEE995BE937ADFE6E1749FD9D7D35A659F95841E5F

Key	Value
MD5	F564B670CC9463C8A525730C7C2EDA71
PackageArch	noarch
PackageDescription	General-purpose OAuth 1.0 authentication strategy for Passport. This module lets you authenticate using OAuth in your Node.js applications. By plugging into Passport, OAuth authentication can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express. Note that this strategy provides generic OAuth support. In many cases, a provider-specific strategy can be used instead, which cuts down on unnecessary configuration, and accommodates any provider-specific quirks. See the list for supported providers. Developers who need to implement authentication against an OAuth provider that is not already supported are encouraged to sub-class this strategy. If you choose to open source the new provider-specific strategy, please add it to the list so other people can find it.
PackageMaintainer	Fedora Project
PackageName	nodejs-passport-oauth1
PackageRelease	1.fc24
PackageVersion	1.1.0
SHA-1	27AB995BF1AEAC7BABC461C985DF9C73AF9D89EA
SHA-256	8699C1917064000F29E7A4E8BCE30B4B6110A1A4E3F499EC18FB4153ACF4CB74

Key	Value
MD5	03FF7BBB1F1E8E226FAD4DF1E0B861D3
PackageArch	noarch
PackageDescription	General-purpose OAuth 1.0 authentication strategy for Passport. This module lets you authenticate using OAuth in your Node.js applications. By plugging into Passport, OAuth authentication can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express. Note that this strategy provides generic OAuth support. In many cases, a provider-specific strategy can be used instead, which cuts down on unnecessary configuration, and accommodates any provider-specific quirks. See the list for supported providers. Developers who need to implement authentication against an OAuth provider that is not already supported are encouraged to sub-class this strategy. If you choose to open source the new provider-specific strategy, please add it to the list so other people can find it.
PackageMaintainer	Fedora Project
PackageName	nodejs-passport-oauth1
PackageRelease	1.fc24
PackageVersion	1.1.0
SHA-1	7A9F9F600B0CF35D19539F3198A922266046E32F
SHA-256	7B1E61ACB1FCF08D33313D70C1DA5138D95DEEC89242636D9EBBC6C5430C4BE0

Key	Value
MD5	3A3AB5F1DEDF0698F448446049A13D2A
PackageArch	noarch
PackageDescription	General-purpose OAuth 2.0 authentication strategy for Passport. This module lets you authenticate using OAuth 2.0 in your Node.js applications. By plugging into Passport, OAuth 2.0 authentication can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express. Note that this strategy provides generic OAuth 2.0 support. In many cases, a provider-specific strategy can be used instead, which cuts down on unnecessary configuration, and accommodates any provider-specific quirks. See the list for supported providers. Developers who need to implement authentication against an OAuth 2.0 provider that is not already supported are encouraged to sub-class this strategy. If you choose to open source the new provider-specific strategy, please add it to the list so other people can find it.
PackageMaintainer	Fedora Project
PackageName	nodejs-passport-oauth2
PackageRelease	8.fc32
PackageVersion	1.4.0
SHA-1	0B58FA9370D338DB45DDB530EB8A819CD0C8CC54
SHA-256	4A083317E130799BD5F18C1FBFE6E1468DE19C2678D3AD394C35F209078F7D8E

Key	Value
FileName	http://archlinux.mirror.root.lu//pool//community//hedgedoc-1.7.2-2-any.pkg.tar.zst
MD5	91078D6D568C1844CCA901FD38E4BB1A
SHA-1	07784E8E1B1485301473FCCCD4C26E7C110C4512
SHA-256	2B0FC74C4902250455F4CA3B12F64BCD24C81CECE443680A791AA699C22E26AE
SSDEEP	1572864:sZvxKOq/J6gYmjd+MlBGL4q2Xs3ynDN8ntjlteI/0bZ5HbvvAZP:c5U/vjXF78iD+tXBqZlbi
TLSH	T1DF1833987F7A6F4ADA9F20FB627719D632C13CC667797446309EB4E080B8B8A5D50313