Result for BCD1DFAA9D5BC61FBA6B313EC3D7AB264C6A6CC2

Query result

Key Value
FileName./usr/lib/node_modules/passport-oauth2/package.json
FileSize1166
MD52948520A4A6F88EA156CC0DA825ACB45
SHA-1BCD1DFAA9D5BC61FBA6B313EC3D7AB264C6A6CC2
SHA-25611BF05015663916FE2E56746599FF2FF316A53C82066965235F6FF7DAE8AC39F
SSDEEP24:gcV1o1KSdGSjobzCvSh/OVdpMeUmi4QiYW2XCtVaNUS:r/o1KyG8oCa8ffUmTx/2MaNUS
TLSHT1FF2129B5E1755C338ECE55A2A8B94142B260894B4C647C0C7B9E672C9F5D8AF32BC28D
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
MD53A3AB5F1DEDF0698F448446049A13D2A
PackageArchnoarch
PackageDescriptionGeneral-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.
PackageMaintainerFedora Project
PackageNamenodejs-passport-oauth2
PackageRelease8.fc32
PackageVersion1.4.0
SHA-10B58FA9370D338DB45DDB530EB8A819CD0C8CC54
SHA-2564A083317E130799BD5F18C1FBFE6E1468DE19C2678D3AD394C35F209078F7D8E