@financial-times/g-deploy
npmIs @financial-times/g-deploy safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @financial-times/g-deploy v4.0.1. Trust score: 85/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)
@financial-times/g-deploy Passed Security Checks
No security concerns detected
0
0
1
Install Scripts Detected
This package runs scripts during installation. Review these scripts before installing.
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.
@financial-times/g-deploy Capabilities & Permissions
What @financial-times/g-deploy can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Process Spawning
This package can spawn child processes.
Environment Variables
Accesses the following environment variables.
AGENTS.md for @financial-times/g-deploy
Good instructions lead to good results. brin adds @financial-times/g-deploy 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 →
@financial-times/g-deploy Documentation & Source Code
For the full @financial-times/g-deploy README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @financial-times/g-deploy safety
Install (safety-checked)
Weekly Downloads
Version
4.0.1License
MITLast Scanned
Trust Score
Install Scripts
This package has install scripts that run automatically:
prepare
Capabilities
Spawns child processes
Accesses: AWS_REGION, BUCKET_NAME, WRITE_VERSIONS_JSON