@orderly.network/trading-points
Complete points system for trading campaigns: points tracking, leaderboards, referral links, and stage management.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ramda | AI (phantom-deps): Ramda declared and used in types/config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@orderly.network/types | AI (phantom-deps): Internal monorepo dep; likely re-exported or used indirectly in this package. | ai | |
| phantom-deps | phantom-dep:@orderly.network/react-app | AI (phantom-deps): Internal monorepo dep; likely re-exported or used indirectly in this package. | ai | |
| phantom-deps | phantom-dep:@orderly.network/ui-connector | AI (phantom-deps): Internal monorepo dep; likely re-exported or used indirectly in this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 2 / 10 | |
| 2.0.1 | 2 / 10 | |
| 2.0.0 | 2 / 10 | |
| 1.5.0 | 2 / 10 | |
| 1.4.4 | 2 / 10 | |
| 1.4.3 | 2 / 10 | |
| 1.4.2 | 2 / 10 | |
| 1.4.1 | 2 / 10 | |
| 1.4.0 | 9 / 12 | |
| 1.3.2 | 9 / 12 | |
| 1.3.1 | 9 / 12 | |
| 1.3.0 | 9 / 12 | |
| 1.2.2 | 9 / 12 | |
| 1.2.1 | 9 / 12 | |
| 1.2.0 | 9 / 12 | |
| 1.1.1 | 9 / 12 | |
| 1.1.0 | 9 / 12 | |
| 1.0.2 | 9 / 12 | |
| 1.0.1 | 9 / 12 | |
| 1.0.0 | 2 / 10 |
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
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.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.