Smallest/simplest possible means of using atob with both Node and browserify
56%
Total Score
50
100
83
75
50
No build attestation or trusted-publisher provenance is present, limiting publication transparency. This is a caution rather than a severe risk because the artifact is simple and contains no runtime dependencies.
The registry lists one publishing maintainer. That is a thin operational base, although the repository is also directly linked to the same individual.
The package has only two releases, with the latest published in June 2017 and none in the last 12 months. This is a meaningful maintenance concern, though a small stable utility may not need frequent releases.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, reinforcing that active maintenance is not evident.
The repository uses no build or security-scanning tooling. This is a minor maintenance and assurance gap, partly offset by the package's small, dependency-free structure.
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.