← Home

boundary

Provides boundary functions, (upper-bound and lower-bound).

2
Versions
BSD-2-Clause
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

constellationazu

Keywords

algorithm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): azu is a well-established npm publisher (250 approved packages) and known textlint ecosystem maintainer; transfer to textlint org is credible and consistent. ai
maintainer-change maintainer-added AI (maintainer-change): azu has a strong track record (250/0 approved/rejected) and is the known textlint org maintainer; this is a legitimate handoff. ai
publish-pattern dormant-publish AI (publish-pattern): Long dormancy followed by revival is explained by azu adopting this utility into the textlint ecosystem; no malicious indicators present. ai

Versions (showing 2 of 2)

Version Deps Published
2.0.0 0 / 6
1.0.1 0 / 10

v2.0.0

2 findings
HIGH Publisher changed: constellation → azu (on 2023-01-07) provenance

This version was published by a different npm account than previous versions on 2023-01-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.1

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.