bigdecimal
Arbitrary-precision BigInteger and BigDecimal real numbers: Apache Harmony's implementation
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:iriscouch.com | AI (email-domain): Package is ~15 years old, essentially unmaintained/stable with only 2 versions. Domain lapse is a latent risk but no active exploit; package content is clean with no deps or install scripts. | ai | |
| provenance | no-provenance | AI (provenance): Package is 14+ years old, predates Sigstore provenance; stable, no install scripts, no material risk from missing attestation. | ai |
v0.6.1
2 findingsMaintainer email '[email protected]' uses domain 'iriscouch.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsMaintainer email '[email protected]' uses domain 'iriscouch.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.