@gooddollar/goodcollective-contracts
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:typechain-types/factories/contracts/DirectPayments/DirectPaymentsFactory__factory.ts | AI (source-diff): Contract bytecode hex string in autogenerated typechain output, not a payload. | ai | |
| source-diff | encoded-string-file:typechain-types/factories/contracts/UBI/UBIPoolFactory__factory.ts | AI (source-diff): Contract bytecode hex string in autogenerated typechain output, not a payload. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher lbwgd is a known maintainer from prior approved versions. | ai | |
| source-diff | obfuscated-file:typechain-types/factories/contracts/UBI/UBIPool__factory.ts | AI (source-diff): Autogenerated typechain factory file; long lines are ABI/bytecode, not obfuscation. | ai | |
| source-diff | encoded-string-file:typechain-types/factories/contracts/utils/HelperLibrary__factory.ts | AI (source-diff): Contract bytecode hex string in autogenerated typechain output, not a payload. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Same rationale — contracts artifact package, missing description is benign here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Contracts artifact package under established GoodDollar org; sparse metadata is normal for this package type. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.4.2 | 0 / 34 | |
| 1.4.1 | 0 / 34 | |
| 1.4.0 | 0 / 36 | |
| 1.3.1 | 0 / 36 | |
| 1.3.0 | 0 / 36 | |
| 1.2.0 | 0 / 36 | |
| 1.1.0 | 0 / 36 |
v1.3.0
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lbwgd) than the most recent previously approved version (sirpush) on 2025-01-31, but lbwgd 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.