Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md porcentaje, un ORO o un veredicto: todo sale de `scripts/motor.mjs`. Si escribes una conclusión con
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a coherent Instagram content-analysis workflow, but it includes under-scoped fallback collection paths that could be used on accounts beyond the stated owner-controlled use case.
Install only if you intend to use it for an account you control or have explicit consent to analyze. Prefer the Composio connected-account path, avoid the unofficial Instagram scraping recipe, and be aware the generated datos.json and HTML report may contain private business metrics and should be stored/shared carefully.
Referenced artifact was not completely inspected
porcentaje, un ORO o un veredicto: todo sale de `scripts/motor.mjs`. Si escribes una conclusión con
Referenced artifact was not completely inspected
un número, cópialo del `resultado.json`. El validador de `render.mjs` rechaza lo que contradiga al motor.
Referenced artifact was not completely inspected
- **formato** = el MOLDE, con el `nombre` exacto de `references/formatos.json` (186 de la Biblioteca). Si ninguno encaja, descríbelo con palabras de mecánica, n
Referenced artifact was not completely inspected
- **formato** = el MOLDE, con el `nombre` exacto de `references/formatos.json` (186 de la Biblioteca). Si ninguno encaja, descríbelo con palabras de mecánica, n
Referenced artifact was not completely inspected
- **formato** = el MOLDE, con el `nombre` exacto de `references/formatos.json` (186 de la Biblioteca). Si ninguno encaja, descríbelo con palabras de mecánica, n
The skill says it should only be used for the student’s own account with her statistics, but it also documents a fallback that can pull public Instagram data for any handle via Apify. That creates a privacy and authorization gap: an operator could analyze a third party’s account without consent, contrary to the stated restriction, and normalize collection of profile data outside the intended trust boundary.
The instruction 'Todo lo que lee va en tú (nunca vos)' imposes a specific language/locale variant on all output. This is a natural-language policy concern because it removes user choice about dialect/register and is not documented as a justified regional compliance requirement.
The code forces all numeric and date formatting to use the "es-CO" locale via toLocaleString and toLocaleDateString. This is a natural-language/locale policy issue because the file does not offer user opt-in, fallback, or any documented reason that the report must be rendered specifically for Colombian Spanish users.
SQP-3 applies to all file types and covers natural-language language/locale policy violations. This JSON defines skill content fields and long-form instructional text exclusively in Spanish, with no indication that the skill is region-specific or that users can opt into that language.
This code file contains extensive user-facing instructional text and labels exclusively in Spanish, such as the header comments and explanatory strings. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified.
The documentation presents Apify as a limited fallback, but later normalizes direct GraphQL/API scraping of Instagram endpoints as a working acquisition method. Even if framed operationally, these instructions encourage collection through unofficial interfaces that may bypass platform controls, increase legal/compliance risk, and make it easier to fetch data outside properly authorized integrations.