alibabacloud-idaas-ad-ldap-integration@0.0.1
CAUTIONPublisher claims: "Use when asked for AD/OpenLDAP-to-IDaaS inbound integration and existing identity-provider reconciliation, including CLI tool availability checks, CLI or Manual console onboarding, TLS/schema and mapping verification, scoped user/OU/group synchronization, directory-password login verification with TwoFactor distinguished from full portal login, complete or incomplete offline sync-export evidence reviews (job counters versus current inventory, partial_success and email conflicts), readiness and permission checklists, CLI-to-Manual fallback, and historical handover reports covering deletion and surviving objects. Also use for prerequisite-only local aliyun/ldapsearch availability (aliyun version, ldapsearch -VV) and offline partial_success/email-conflict diagnosis without live access. 用于只检查本机工具可用性及离线分析,不要求开始接入。" Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-02 and scored it 53/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Auto-update or dynamic fetch configuration; Auto-update or dynamic fetch configuration; Auto-update or dynamic fetch configuration. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
What would make this Verified
27 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim sdk-team: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Prompting user to enter sensitive credentials≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- Unicode escape sequence detected≈ +2 on the totalPut hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.