tailwindcss-animate-catalog
A configurable, namespaced Animate.css integration for Tailwind CSS
This report shows the evidence for tailwindcss-animate-catalog@2.0.7. 2 of 2 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18085 confirms this npm version as malicious.
Independent LPM AI assessment
Manual ReviewIndependent AI assessment: manual_review. LPM AI review remains unresolved.
The package source connects style generation to a scoped registry dependency whose source is unavailable in this snapshot. That unresolved executable boundary prevents a clean determination, but the inspected source does not establish malicious behavior.
Independent scan evidence
public snapshot- package.json declares the unresolved registry dependency @jasperquinn/postcss-motion-helpers at ^1.0.1.
- Plugin style generation calls buildVariables, which loads and invokes that dependency as a PostCSS plugin; its source is unavailable for review.
Source & flagged code
6 flagged · loading sourcepackage.json declares the unresolved registry dependency @jasperquinn/postcss-motion-helpers at ^1.0.1.
package.jsonView on unpkg · L32Plugin style generation calls buildVariables, which loads and invokes that dependency as a PostCSS plugin; its source is unavailable for review.
index.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to tailwindcss-animate-catalog@2.0.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing tailwindcss-animate-catalog@2.0.7. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.