express-http-to-https
npmIs express-http-to-https safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for express-http-to-https v1.1.4. Trust score: 65/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.
Install (safety-checked)
express-http-to-https Passed Security Checks
No security concerns detected
0
0
0
No Concerns Detected
No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.
This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.
express-http-to-https Capabilities & Permissions
What express-http-to-https can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Network Access
This package makes network requests.
Environment Variables
Accesses the following environment variables.
AGENTS.md for express-http-to-https
Good instructions lead to good results. brin adds express-http-to-https documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
express-http-to-https Documentation & Source Code
For the full express-http-to-https README, API documentation, and source code, visit the official package registry.
Frequently asked questions about express-http-to-https safety
Install (safety-checked)
Weekly Downloads
Version
1.1.4License
MITLast Scanned
Trust Score
Capabilities
Makes network requests
Accesses: NODE_TLS_REJECT_UNAUTHORIZED