allure-js-commons
npmIs allure-js-commons safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for allure-js-commons v3.4.5. 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)
allure-js-commons 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.
allure-js-commons Capabilities & Permissions
What allure-js-commons can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Filesystem Access
Reads from the filesystem.
Environment Variables
Accesses the following environment variables.
AGENTS.md for allure-js-commons
Good instructions lead to good results. brin adds allure-js-commons 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 →
allure-js-commons Documentation & Source Code
For the full allure-js-commons README, API documentation, and source code, visit the official package registry.
Frequently asked questions about allure-js-commons safety
Install (safety-checked)
Weekly Downloads
Version
3.4.5License
Apache-2.0Last Scanned
Trust Score
Capabilities
Reads files
Accesses: ALLURE_TESTPLAN_PATH, ALLURE_TEST_MODE