@colijnit/transactionapi
public api for ione backend specific for transactions and version 2.6.0
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:rxjs-compat | AI (dependencies): rxjs-compat is a well-known RxJS compatibility shim; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Declared dep used via config/indirect import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:jsencrypt | AI (phantom-deps): Declared dep used via config/indirect import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:rxjs-compat | AI (phantom-deps): Declared dep used via config/indirect import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): Known implicit runtime dependency for TypeScript decorators; stable for this package. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 300.1.3 | 5 / 15 | |
| 300.1.2 | 5 / 15 | |
| 300.1.1 | 5 / 15 | |
| 300.1.0 | 5 / 15 | |
| 262.1.14 | 5 / 15 | |
| 262.1.13 | 5 / 15 | |
| 262.1.12 | 5 / 15 | |
| 262.1.11 | 5 / 14 | |
| 262.1.10 | 5 / 14 | |
| 262.1.9 | 5 / 14 | |
| 262.1.8 | 5 / 14 | |
| 262.1.7 | 5 / 14 | |
| 262.1.6 | 5 / 14 | |
| 262.1.4 | 5 / 14 | |
| 262.1.3 | 5 / 14 | |
| 262.1.2 | 5 / 14 | |
| 262.1.1 | 5 / 14 | |
| 261.1.27 | 5 / 13 | |
| 261.1.26 | 5 / 13 | |
| 261.1.25 | 5 / 13 | |
| 261.1.24 | 5 / 13 | |
| 261.1.23 | 5 / 13 | |
| 261.1.22 | 5 / 13 | |
| 261.1.21 | 5 / 13 | |
| 261.1.20 | 5 / 13 | |
| 261.1.19 | 5 / 14 | |
| 261.1.17 | 5 / 14 | |
| 261.1.16 | 5 / 14 | |
| 261.1.15 | 5 / 14 | |
| 261.1.10 | 5 / 14 | |
| 261.1.9 | 5 / 14 | |
| 261.1.8 | 5 / 14 | |
| 261.1.7 | 5 / 14 | |
| 261.1.5 | 5 / 14 | |
| 261.1.3 | 5 / 14 | |
| 261.1.1 | 5 / 14 | |
| 260.1.27 | 5 / 14 | |
| 260.1.26 | 5 / 14 | |
| 260.1.25 | 5 / 14 | |
| 260.1.24 | 5 / 14 | |
| 260.1.23 | 5 / 14 | |
| 260.1.18 | 5 / 14 | |
| 260.1.16 | 5 / 14 | |
| 260.1.7 | 5 / 14 | |
| 260.1.6 | 5 / 14 | |
| 260.1.5 | 5 / 14 | |
| 259.1.26 | 5 / 14 | |
| 259.1.25 | 5 / 14 |
v300.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (patrickvkeulen) than the most recent previously approved version (elske) on 2026-07-27, but patrickvkeulen 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.
v300.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (goran_silic_colijn) than the most recent previously approved version (elske) on 2026-07-22, but goran_silic_colijn 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.
v300.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (elske) than the most recent previously approved version (ralf.eversen) on 2026-07-15, but elske 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.
v300.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ralf.eversen) than the most recent previously approved version (goran_silic_colijn) on 2026-07-13, but ralf.eversen 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.
v262.1.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (elske) than the most recent previously approved version (daan.vdj) on 2026-07-16, but elske 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.
v262.1.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (goran_silic_colijn) than the most recent previously approved version (patrickvkeulen) on 2026-07-03, but goran_silic_colijn 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.
v261.1.27
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (daan.vdj) than the most recent previously approved version (elske) on 2026-07-16, but daan.vdj 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.