@factordao/sdk
Factor SDK is a collection of tools and libraries for building Factor applications.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:ethereum.email | AI (email-domain): Cosmetic maintainer email quirk, no takeover behavior observed; monitor for future domain registration. | ai | |
| dependencies | unvetted-dep:@factordao/contracts | AI (dependencies): First-party sibling package under same npm scope/org. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Used in scripts/config, common false positive. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Used via graphql-request, common false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.4.59 | 11 / 28 | |
| 1.2.11 | 11 / 28 | |
| 1.1.4 | 11 / 29 | |
| 1.1.3 | 10 / 31 |
v1.4.59
3 findingsMaintainer email '[email protected]' uses domain 'ethereum.email' 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.
This version was published by a different npm account (factor_fi) than the most recent previously approved version (turinglabsorg) on 2024-10-21, but factor_fi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.11
3 findingsMaintainer email '[email protected]' uses domain 'ethereum.email' 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.
This version was published by a different npm account (factor_fi) than the most recent previously approved version (turinglabsorg) on 2024-08-08, but factor_fi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.