binary-search
tiny binary search function with comparators
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate org transition from Dark Sky (defunct company) to ironwallaby (trusted publisher, 24 approved pkgs). Change occurred in 2018. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from darkskyapp to ironwallaby in 2018 as part of Dark Sky's internal reorg; ironwallaby is a trusted long-standing publisher. | ai | |
| email-domain | unclaimed-email:darkskyapp.com | AI (email-domain): Dark Sky was acquired by Apple and shut down; domain lapse is expected. Stale metadata, no active npm auth risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (ironwallaby, jeffbyrnes, darkskybot) are part of the original Dark Sky team; transition is stable since 2018. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): darkskyapp org account removed as part of legitimate maintainer transition; stable since 2018. | ai | |
| provenance | no-provenance | AI (provenance): Legacy package from a defunct company; provenance attestation is not expected and won't be added. Stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.3.6 | 0 / 2 | |
| 1.3.5 | 0 / 2 | |
| 1.3.4 | 0 / 2 | |
| 1.3.3 | 0 / 2 | |
| 1.3.2 | 0 / 2 | |
| 1.3.1 | 0 / 2 | |
| 1.3.0 | 0 / 2 | |
| 1.2.0 | 0 / 2 | |
| 1.1.2 | 0 / 2 | |
| 1.1.1 | 0 / 2 | |
| 1.1.0 | 0 / 2 | |
| 1.0.2 | 0 / 2 | |
| 1.0.1 | 0 / 2 | |
| 1.0.0 | 0 / 2 |
v1.3.6
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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.
v1.3.5
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
4 findingsAll previous maintainers (darkskyapp) were replaced by new maintainers (darkskybot, ironwallaby, jeffbyrnes). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2018-06-25. This could indicate a legitimate maintainer transition or an account compromise.
Maintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
4 findingsAll previous maintainers (darkskyapp) were replaced by new maintainers (ironwallaby, jeffbyrnes, darkskybot). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2018-01-29. This could indicate a legitimate maintainer transition or an account compromise.
Maintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsMaintainer email '[email protected]' uses domain 'darkskyapp.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.