Coding standard for Netgen packages
67%
Total Score
caution
Usable with caveats: no recent commits and a workflow uses an unpinned container image.
There are only two releases over about 285 days, with releases roughly 125 days apart. That is sparse evidence of ongoing maintenance, although the package may be intentionally stable.
The repository recorded zero commits and zero active maintainers during the last three months. This weakens evidence of active maintenance, though it is partly offset by the recent release.
Composer is used for the build, which fits the package ecosystem, but no security scanning tooling is reported. For a small configuration package this is a modest transparency gap rather than a severe concern.
The repository has no security policy. That limits disclosure guidance, although the package is a small development-time coding-standard configuration rather than a security-sensitive runtime library.
Both workflows were analyzed completely and have no untrusted checkout or script-injection findings, but all four action references are unpinned and the audit found a high-confidence unpinned container image. This is a workflow supply-chain hygiene concern, not a standalone reason to reject the package.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.