Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
oodelally
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Track what top investors own (13F) and why they own it (10K AI Analysis)
(superinvestorsbelike.com)
3 points
by
oodelally
7mo ago
|
0 comments
2.
▲
Cheatsheet to Rewrite Git History
(blog.gitguardian.com)
6 points
by
oodelally
6y ago
|
0 comments
3.
▲
The threat of leaked secrets in Git repos
(reddit.com)
1 points
by
oodelally
6y ago
|
0 comments
4.
▲
An alternative to truffleHog to detect leaked secrets
(gitguardian.com)
1 points
by
oodelally
6y ago
|
0 comments
5.
▲
How does SAP scan Git repos for secrets?
(blog.gitguardian.com)
1 points
by
oodelally
6y ago
|
0 comments
6.
▲
Secrets detection must be part of your DevOps pipeline
(gitguardian.com)
2 points
by
oodelally
6y ago
|
0 comments
7.
▲
Secrets detection must be part of your DevOps pipeline
(gitguardian.com)
1 points
by
oodelally
6y ago
|
0 comments
8.
▲
Secrets detection handbook for dev, SEC, ops
(gitguardian.com)
1 points
by
oodelally
6y ago
|
0 comments
9.
▲
by
oodelally
6y ago
Not the current state of the world!
10.
▲
by
oodelally
6y ago
No you can add and delete without going through code review. And this is was happens most of the time as we're all constantly committing deletions and additions that we push on a feature branch for example before it is being reviewed a
11.
▲
by
oodelally
6y ago
Even if the secret is added then deleted?
12.
▲
Why are secrets in Git such a threat?
(gitguardian.com)
14 points
by
oodelally
6y ago
|
0 comments
13.
▲
Why is it hard to detect API keys in source code?
(gitguardian.com)
14 points
by
oodelally
6y ago
|
9 comments
14.
▲
Why automate secrets scanning throughout your SDLC?
(gitguardian.com)
14 points
by
oodelally
6y ago
|
0 comments
15.
▲
Humoristic DevSecOps glossary with funny cartoons
(blog.gitguardian.com)
1 points
by
oodelally
6y ago
|
0 comments
16.
▲
GitGuardian raises $12M to help developers write more secure code
(techcrunch.com)
2 points
by
oodelally
7y ago
|
0 comments
17.
▲
GitGuardian raises $12M to find sensitive data hidden in online code
(venturebeat.com)
1 points
by
oodelally
7y ago
|
0 comments
18.
▲
Secrets leaked on GitHub
(cloudpro.co.uk)
3 points
by
oodelally
7y ago
|
0 comments
19.
▲
GitHub security: you thought your company was safe on GitHub?
(blog.gitguardian.com)
1 points
by
oodelally
7y ago
|
0 comments
20.
▲
GitHub security: you thought your company was safe on GitHub?
(blog.gitguardian.com)
1 points
by
oodelally
7y ago
|
0 comments
21.
▲
Leak Mitigation Checklist
(github.com)
32 points
by
oodelally
8y ago
|
4 comments
22.
▲
More than 3,000 api keys leaked per day on GitHub
(blog.gitguardian.com)
3 points
by
oodelally
8y ago
|
0 comments
23.
▲
One year and a half scanning GitHub for sensitive data
(blog.gitguardian.com)
10 points
by
oodelally
8y ago
|
0 comments