← Home

any-base

npm Repository Homepage

Converter from any base to other any base

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mifczu

Keywords

numberconvertbasealphabetshort numberlong numbersdechexbinoctany

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/any-base.js AI (source-diff): Standard Browserify bundle output for browser distribution; build script in package.json confirms this. Not obfuscation. ai
source-diff source-size-tripled AI (source-diff): Size increase is from adding dist/ build artifacts (Browserify bundle). Expected for a package adding browser support. ai

Versions (showing 3 of 3)

Version Deps Published
1.1.0 0 / 4
1.0.1 0 / 3
1.0.0 0 / 0

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

2 findings
HIGH New obfuscated file: dist/any-base.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.