@ploomescrm/ui@3.5.0
Biblioteca de componentes React do Design System da Ploomes: componentes acessíveis, tematizáveis e prontos para produção, com tokens de design embutidos e suporte a dark mode e whitelabel em tempo de execução.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe automatic postinstall mutation of a consumer's Claude configuration leaves an agent extension lifecycle risk, so a warning is appropriate. The installed, package-owned guidance is UI-library-specific, and inspected source does not support blocking the package as malicious.
Decision evidence
public snapshot- package.json runs scripts/setup.mjs automatically as a postinstall hook.
- The setup script runs for installed dependencies and copies package extensions into the consuming project's .claude directories.
- The setup script removes and replaces entries with this package's prefix, then adds its extension files.
- The package also places a reference to its own Claude instructions at the top of the consumer's .claude/CLAUDE.md.
- The installed skills provide setup guidance and component documentation for @ploomescrm/ui.
- The extensions are package-owned and focused on configuring and documenting this UI library.
- The setup uses a package-specific prefix and preserves consumer content outside its marked block; the inspected setup source shows no network transfer.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs scripts/setup.mjs automatically as a postinstall hook.
package.jsonView on unpkg · L75Findings
Affected versions and remediation
This report applies to @ploomescrm/ui@3.5.0.
See all versions of @ploomescrm/ui for other recorded verdicts.
- Review the evidence and your use of @ploomescrm/ui@3.5.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.