-
๐ ๐ข๐ญ ๐ฅ๐จ๐ --๐๐ฎ๐ญ๐ก๐จ๐ซ="<๐๐ฎ๐ญ๐ก๐จ๐ซ>": Shows commits authored by the specified author.
-
๐ ๐ข๐ญ ๐๐ข๐๐ --๐ง๐๐ฆ๐-๐จ๐ง๐ฅ๐ฒ: Shows only the names of files that have differences between two commits or branches.
-
๐ ๐ข๐ญ ๐ฉ๐ซ๐ฎ๐ง๐: Removes unreachable objects and refs from the local repository.
-
๐ ๐ข๐ญ ๐๐ข๐๐ --๐ฌ๐ญ๐๐ ๐๐: Show the differences between the staging area and the last commit.
-
๐ ๐ข๐ญ ๐ซ๐๐๐ฅ๐จ๐ : Shows a log of all the changes made to the refs (branches, tags) in the repository.
As a security professional, it is important to conduct a thorough reconnaissance. With the increasing use of APIs nowadays, it has become paramount to keep access tokens and other API-related secrets secure in order to prevent leaks. However, despite technological advances, human error remains a factor, and many developers still unknowingly hardcode their API secrets into source code and commit them to public repositories. GitHub, being a widely popular platform for public code repositories, may inadvertently host such leaked secrets. To help identify these vulnerabilities, I have created a comprehensive search list using powerful search syntax that enables the search of thousands of leaked keys and secrets in a single search.
(path:*.{File_extension1} OR path:*.{File_extension-N}) AND ({Keyname1} OR {Keyname-N}) AND (({Signature/pattern1} OR {Signature/pattern-N}) AND ({PlatformTag1} OR {PlatformTag-N}))
**1.
/ App1 - Docker container 1 | |
const App1 = () => <div>App 1</div>; | |
export const getFederatedModule = name => { | |
return { | |
'./App1': App1 | |
}; | |
}; |
// App1 | |
const App1 = () => <div>App 1</div>; | |
export const bootstrap = [App1]; | |
export const mount = [App1]; | |
export const unmount = [App1]; | |
// App2 |