-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add har recorder #181
Add har recorder #181
Conversation
@pes10k Can confirm, branch still works as expected. |
fc59bfd
to
2e89553
Compare
2e89553
to
e8ae1ad
Compare
@pes10k I don't have the access rights to push here. Added tests to my fork https://github.com/FHantke/pagegraph-crawl/tree/add-har-recorder |
[puLL-Merge] - brave/pagegraph-crawl@181 DescriptionThis PR introduces several significant changes to the pagegraph-crawl project, including the addition of HAR (HTTP Archive) generation functionality, improvements to the testing process, and updates to dependencies and documentation. ChangesChanges
sequenceDiagram
participant User
participant CLI
participant Puppeteer
participant Browser
participant HARGenerator
participant FileSystem
User->>CLI: Run crawl command
CLI->>Puppeteer: Launch browser
Puppeteer->>Browser: Create new page
CLI->>HARGenerator: Prepare HAR recording
Browser->>HARGenerator: Send network events
Browser->>FileSystem: Generate PageGraph
HARGenerator->>FileSystem: Generate HAR file
FileSystem->>User: Save output files
Possible Issues
Security Hotspots
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is a deprecated package?The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed. Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
@@ -0,0 +1,4 @@ | |||
<svg height="100" width="100" xmlns="http://www.w3.org/2000/svg"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reported by reviewdog 🐶
[safesvg] element svg: validity error : Element svg content does not follow the DTD, expecting (desc | title | metadata | animate | set | animateMotion | animateColor | animateTransform | svg | g | defs | symbol | use | switch | image | style | path | rect | circle | line | ellipse | polyline | polygon | text | altGlyphDef | marker | color-profile | linearGradient | radialGradient | pattern | clipPath | mask | filter | cursor | a | view | script | font | font-face | foreignObject)*, got (circle CDATA)
Run SVGO on your assets
Cc @thypon @kdenhartog
b32d9d3
to
ae8b73a
Compare
this repo has some deprecated dependencies that should be addressed (see the socket comment above) |
@diracdeltas these are just dev dependencies, and all pulled in from If not, is there an alternative security recommends other than standardjs? IIRC it was either suggested or required for all code for a while. I can search for something kept more up to date, but if any suggestions greatly appreciated |
we do use standard in basically all js repos but i haven't seen these issues. they might be false positives then. |
package.json
Outdated
"eslint": "9.16.0", | ||
"express": "4.21.1", | ||
"express": "^4.21.2", | ||
"standard": "^17.1.2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these updated deps should be pinned to exact versions instead of using ^
Hmm, odd, I don't think they're false positives. The current version of Are those other projects configured differently? Would really like to not need to remove |
5605d9c
to
ce01a2a
Compare
ce01a2a
to
ea6c82f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Discussing what to do with socket.io warnings in other channels
Continues #180