Caveat verdict

linkedin-email-phone-apify

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

LinkedIn contact enrichment via Apify actors using a user-provided APIFY_TOKEN; runs two documented Apify actors to extract phone and email data, which is the stated and transparent purpose.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

65
security
80
transparency
70
maintenance

Findings (3)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · TOKEN='apify_api_xxx

Pattern match low

Python urllib.request — network access

scripts/linkedin_email_phone_pipeline.py · prose · downgraded · urllib.request

Pattern match low

Python os.getenv — reads environment variable

scripts/linkedin_email_phone_pipeline.py · prose · downgraded · os.getenv(

Permissions & capabilities

Requires 1 environment variable. (1 sensitive: APIFY_TOKEN).

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API