@kodiak-finance/orderly-affiliate
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-removed | AI (maintainer-change): Active monorepo with frequent releases; maintainer rotation is expected and publisher is a known maintainer. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the @kodiak-finance namespace; consistent pattern, not a per-version concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo component; sparse metadata is consistent across all @kodiak-finance/orderly-* packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; missing description is a stable pattern across this namespace. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.9.4 | 10 / 8 | |
| 2.8.12 | 10 / 8 | |
| 2.8.8 | 10 / 8 | |
| 2.8.7 | 10 / 8 |
v2.9.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bards) than the most recent previously approved version (xsubject) on 2026-06-16, but bards 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.
v2.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.