← Home

@colijnit/transaction

npm Repository Homepage

Colijn IT transaction module for Angular 20

51
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

patrickvkeulenralf.eversendaan.vdjelskedeyan_colijnityury.sjilliscitjkruijtgoran_silic_colijn

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:esm2015/colijnit-transaction.js AI (source-diff): Angular ng-packagr esm2015 bundle output, not true obfuscation; samples show plain readable code. ai
source-diff large-new-source-files AI (source-diff): Angular ngc build emits many ESM/fesm/umd artifacts; benign for this library. ai
source-diff source-size-tripled AI (source-diff): Compiled Angular bundles + dictionaries inflate size; not injected payload. ai
provenance missing-githead AI (provenance): Manual publish by known maintainer elske, consistent with prior approvals. ai
source-diff obfuscated-file:esm2015/lib/component/add-product/add-product.component.js AI (source-diff): Angular-compiled long-line ESM output, not obfuscation; readable source. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): 127.0.0.1 localhost URLs in unit test fixtures. ai
source-diff net-exec-file:src/lib/threedconfigurator-standalone.bundle.min.js AI (source-diff): Webpack-bundled 3D-configurator dist with GTM loader; build output, not a dropper. ai
semgrep semgrep:child-process-import AI (semgrep): child_process in local build-bundles script, expected for Angular build tooling. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a declared runtime dependency used implicitly by Angular compiled output; stable false positive for this package. ai

Versions (showing 51 of 151)

View all versions
Version Deps Published
300.1.3 1 / 0
300.1.2 1 / 0
300.1.1 1 / 0
300.1.0 1 / 0
262.1.32 1 / 0
262.1.31 1 / 0
262.1.30 1 / 0
262.1.29 1 / 0
262.1.28 1 / 0
262.1.27 1 / 0
262.1.26 1 / 0
262.1.25 1 / 0
262.1.24 1 / 0
262.1.23 1 / 0
262.1.22 1 / 0
262.1.21 1 / 0
262.1.20 1 / 0
262.1.19 1 / 0
262.1.18 1 / 0
262.1.17 1 / 0
262.1.16 1 / 0
262.1.15 1 / 0
262.1.14 1 / 0
262.1.13 1 / 0
262.1.12 1 / 0
262.1.11 1 / 0
262.1.10 1 / 0
262.1.9 1 / 0
262.1.8 1 / 0
262.1.7 1 / 0
262.1.6 1 / 0
262.1.5 1 / 0
262.1.4 1 / 0
262.1.3 1 / 0
262.1.2 1 / 0
262.1.1 1 / 0
262.1.0 1 / 0
261.20.63 1 / 0
261.20.62 1 / 0
261.20.61 1 / 0
261.20.60 1 / 0
261.20.59 1 / 0
261.20.58 1 / 0
261.20.57 1 / 0
261.20.56 1 / 0
261.20.55 1 / 0
261.20.54 1 / 0
261.20.53 1 / 0
261.20.52 33 / 20
261.20.51 1 / 0
261.20.50 1 / 0

v300.1.3

3 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: daan.vdj.

INFO Publisher changed: goran_silic_colijn → daan.vdj (on 2026-07-26, known maintainer) provenance

This version was published by a different npm account (daan.vdj) than the most recent previously approved version (goran_silic_colijn) on 2026-07-26, 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.

v300.1.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: daan.vdj → goran_silic_colijn (on 2026-07-22, known maintainer) provenance

This version was published by a different npm account (goran_silic_colijn) than the most recent previously approved version (daan.vdj) 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 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: ralf.eversen → elske (on 2026-07-15, known maintainer) provenance

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 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jkruijt → ralf.eversen (on 2026-07-14, known maintainer) provenance

This version was published by a different npm account (ralf.eversen) than the most recent previously approved version (jkruijt) on 2026-07-14, 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.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v262.1.31

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: daan.vdj.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jkruijt → daan.vdj (on 2026-07-13, known maintainer) provenance

This version was published by a different npm account (daan.vdj) than the most recent previously approved version (jkruijt) on 2026-07-13, 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.

v262.1.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v262.1.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v262.1.28

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: elske → goran_silic_colijn (on 2026-07-03, known maintainer) provenance

This version was published by a different npm account (goran_silic_colijn) than the most recent previously approved version (elske) 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.

v262.1.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v262.1.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v261.20.63

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: daan.vdj → elske (on 2026-07-17, known maintainer) provenance

This version was published by a different npm account (elske) than the most recent previously approved version (daan.vdj) on 2026-07-17, 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.

v261.20.62

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: daan.vdj.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: elske → daan.vdj (on 2026-07-16, known maintainer) provenance

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.

v261.20.61

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: daan.vdj.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: ralf.eversen → daan.vdj (on 2026-07-15, known maintainer) provenance

This version was published by a different npm account (daan.vdj) than the most recent previously approved version (ralf.eversen) on 2026-07-15, 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.

v261.20.60

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: elske → jkruijt (on 2026-07-10, known maintainer) provenance

This version was published by a different npm account (jkruijt) than the most recent previously approved version (elske) on 2026-07-10, but jkruijt 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.20.59

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jkruijt → elske (on 2026-07-09, known maintainer) provenance

This version was published by a different npm account (elske) than the most recent previously approved version (jkruijt) on 2026-07-09, 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.

v261.20.58

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: goran_silic_colijn → jkruijt (on 2026-07-09, known maintainer) provenance

This version was published by a different npm account (jkruijt) than the most recent previously approved version (goran_silic_colijn) on 2026-07-09, but jkruijt 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.20.57

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v261.20.52

6 findings
HIGH New file with network + code execution: src/lib/threedconfigurator-standalone.bundle.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.

HIGH shady-links-raw-ip: src/transaction.unit.test.ts:12 semgrep

HTTP request to raw IP address — legitimate packages use domain names Source: https://github.com/npm/npm/blob/1be04111b0e653a35d753b5881db81d4f52d282c/src/transaction.unit.test.ts#L12 10 | 11 | const localOptions: Options = { > 12 | url: "http://127.0.0.1:8080/ione", 13 | ajaxUrl: "http://127.0.0.1:8080/ione", 14 | schema: "815",

HIGH shady-links-raw-ip: src/transaction.unit.test.ts:13 semgrep

HTTP request to raw IP address — legitimate packages use domain names Source: https://github.com/npm/npm/blob/1be04111b0e653a35d753b5881db81d4f52d282c/src/transaction.unit.test.ts#L13 11 | const localOptions: Options = { 12 | url: "http://127.0.0.1:8080/ione", > 13 | ajaxUrl: "http://127.0.0.1:8080/ione", 14 | schema: "815", 15 | version: "251",

HIGH shady-links-raw-ip: src/transaction.unit.test.ts:22 semgrep

HTTP request to raw IP address — legitimate packages use domain names Source: https://github.com/npm/npm/blob/1be04111b0e653a35d753b5881db81d4f52d282c/src/transaction.unit.test.ts#L22 20 | 21 | const remoteOptions: Options = { > 22 | url: "http://130.62.7.180:8082/ione", 23 | schema: "815", 24 | version: "251",

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jkruijt → goran_silic_colijn (on 2026-06-20, known maintainer) provenance

This version was published by a different npm account (goran_silic_colijn) than the most recent previously approved version (jkruijt) on 2026-06-20, 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.