@segment/records
Segment Record API client
1
Versions
UNLICENSED
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
jaredperrymccabe615craigarendtjlee9595segment-danielstjulessperand-ioalbert.segmenttamarrowejcxjeroenransijnjoeybloggsmynameiskirmaxence-charriereboggsboggscodenameatlasnettofarahmyclammwdrfouadachille-rousselperipheralcalvinfodfuentesanoonannielstladanazitarbransonjedwatsonsrthurmanjgershenivoloccnixontidothegreatemilyluckettechrisbutterylambtronthehydroimpulseyieldstherebelrobotreinpkdominicbarnesstevenmiller888hanothantejasmanoharrownostephenmathiesontonyxiaosegmentiosegment-admin
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:s1gnalcha0s.com | AI (email-domain): Long-established Segment package with strong publisher track record; domain issue is a stale maintainer email, not an active threat vector. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.35 | 7 / 7 |
v0.0.35
2 findings
HIGH
Unclaimed maintainer email domain: s1gnalcha0s.com
email-domain
Maintainer email '[email protected]' uses domain 's1gnalcha0s.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
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.