GitHub OAuth Device authentication strategy for JavaScript
82%
Total Score
88
100
100
75
100
All 3 recent commits came from one contributor, giving that person 100% of the recent commit share. Organizational ownership helps provide continuity, but no second recent contributor is shown, so this remains a maintenance-resilience concern.
The repository has no published security policy. That is a transparency and vulnerability-reporting gap, though it is moderated by the presence of CodeQL scanning in the project tooling.
All 6 workflows were analyzed successfully and no audit findings or untrusted checkouts were reported; the pull_request_target triggers are therefore not dangerous on their own. However, all 14 action references are unpinned and two workflows grant top-level write permissions, creating a workflow hygiene concern without a demonstrated untrusted sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@octokit/types Version ^18.0.0 | — | — |
@octokit/request Version ^10.0.16 | — | — |
universal-user-agent Version ^7.0.0 | — | — |
@octokit/oauth-methods Version ^6.0.5 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.