Element descriptors and matchers for @boundaries tools
78%
Total Score
healthy
Healthy, with frequent releases and active repository maintenance outweighing concentrated ownership and workflow hygiene gaps.
No build attestation or trusted publisher is recorded, so consumers have less evidence connecting the published artifact to its source and build process.
One contributor made 85% of the recent commits, so maintenance is concentrated; two additional contributors remain active, partially reducing the continuity risk.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
All 29 action references are unpinned, and the audit reports a high-confidence trusted-publishing concern plus low-confidence cache-poisoning findings. There are no untrusted checkouts or script injections, which limits the severity.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2025-10896 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. @boundaries/elements is vulnerable to Inefficient Regular Expression Complexity in versions 1.1.0 - 1.1.1. | 1.1.0 - 1.1.1 | Low |
| Dependency | Last Release | Score |
|---|---|---|
handlebars Version 4.7.9 | — | — |
micromatch Version 4.0.8 | — | — |
is-core-module Version 2.16.1 | — | — |
eslint-module-utils Version 2.12.1 | — | — |
eslint-import-resolver-node Version 0.3.9 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.