@keystone-next/fields-legacy
npmIs @keystone-next/fields-legacy safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @keystone-next/fields-legacy v25.0.0. Trust score: 75/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)
@keystone-next/fields-legacy 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.
@keystone-next/fields-legacy Capabilities & Permissions
What @keystone-next/fields-legacy can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Filesystem Access
Reads and writes to the filesystem.
Environment Variables
Accesses the following environment variables.
AGENTS.md for @keystone-next/fields-legacy
Good instructions lead to good results. brin adds @keystone-next/fields-legacy 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 →
@keystone-next/fields-legacy Documentation & Source Code
For the full @keystone-next/fields-legacy README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @keystone-next/fields-legacy safety
Install (safety-checked)
Weekly Downloads
Version
25.0.0License
MITLast Scanned
Trust Score
Capabilities
Reads & Writes files
Accesses: NODE_ENV