Security audit
Security checks for vulnerabilities and agentic risk
Review is warranted because the examples can leave children’s private information and reusable login cookies accessible to other local users.
Before running the examples, replace fixed /tmp paths with files in a private temporary directory, use umask 077, restrict the cookie file to mode 600, and remove sensitive pages and cookies afterward. Limit the agent to reads unless you explicitly request the exact comment, invitation, feedback-state change, or preference update. Review the separate parser repository before running its npm commands; that code is absent from this package.
The declared purpose describes retrieving art-related data, with a form POST specifically for login. This chunk instead performs an account-settings mutation: it enables artist-activity notifications and omits news and promotional opt-ins to disable them. Reading and resubmitting profile fields supports that undeclared write capability, not the described art-data retrieval.
The description presents data access and retrieval, with form POST mentioned specifically for login. This code instead sends a Comment field to an artwork endpoint, attempting a state-changing comment submission. Posting comments is not a declared capability; cookie handling and local response storage are supporting implementation details.
The description presents a data-access workflow, with login as a supporting operation. The supplied command instead submits fan details to /members/fanclub/add.asp, attempting to modify fan-club membership or initiate an invitation. Although it uses the declared service and curl, this write operation is not disclosed by the stated retrieval purpose. Whether it succeeds depends on valid session cookies and form values.
The declared purpose describes data access and retrieval, with a login POST for authentication. This request instead submits ConfirmAsRead=Mark as Read to the feedback endpoint, requesting a change to account-associated feedback state. That write capability is not disclosed. Cookie handling and saving the response are supporting implementation details, not separate mismatches.
Session persistence is legitimate here, but the setup pre-creates the cookie file using shell redirection without setting private permissions. Under a common 022 umask and traversable home/cache directories, the jar can be readable by other local users, exposing a session usable for authenticated reads and writes. HttpOnly does not protect cookies stored on disk.
export ARTSONIA_USERNAME=you@example.com export ARTSONIA_PASSWORD='your-password' # or: op read "op://Private/Artsonia/password" JAR=~/.cache/artsonia-cookies.txt mkdir -p ~/.cache # ensure the jar's directory exists on a fresh box : > "$JAR" # fresh jar
Authenticated student information is written to a predictable shared-temporary-directory path without restrictive permissions or cleanup. With a common permissive umask, other local users can read the file; predictable names also create file-precreation risks where operating-system protections permit them. Children's names, schools, and account-linked information make this more sensitive than ordinary cached public HTML.
The manifest describes retrieving Artsonia portfolio data through authenticated requests, but these instructions direct a read-modify-write POST to the account profile, including changing profile fields. Modifying account information or opt-ins is a distinct remote mutation, not an implementation requirement for retrieving the advertised data.
The manifest describes accessing Artsonia data by fetching server-rendered pages. These recipes instead submit comments, send real fan-invitation emails, and mark all of a student's feedback as read. Those are externally visible or persistent changes, not implementation details required to retrieve portfolios, comments, fans, or feedback.
The set_notifications recipe submits the account's whole profile form to change notification preferences, including disabling news and promotional opt-ins. Managing account communication settings is not necessary to access student portfolios or the other Artsonia data named in the manifest.