common feature from Vue Macros.
76%
Total Score
83
89
67
100
All recent commits came from one contributor, creating a real continuity risk. Organization ownership provides some ability to hand maintenance off, so this is a caution rather than a severe abandonment signal.
The repository name does not match this package and its README does not mention the package, so the linkage is less transparent even though it may be a legitimate monorepo sub-package.
The project uses established build and test tooling, but no security-scanning tools were detected. The missing scanning is a modest transparency gap.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented.
All three workflows were analyzed with no audit findings or untrusted sinks, and one scopes permissions at job level. However, all four action references are unpinned, which weakens workflow reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ast-kit Version ^2.1.2 | — | — |
local-pkg Version ^1.1.2 | — | — |
unplugin-utils Version ^0.3.0 | — | — |
magic-string-ast Version ^1.0.2 | — | — |
@vue/compiler-sfc Version ^3.5.22 | — | — |
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.