@colijnit/transaction
Colijn IT transaction module for Angular 20
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 | 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)
| Version | Deps | Published |
|---|---|---|
| 260.1.53 | 1 / 0 | |
| 260.1.52 | 1 / 0 | |
| 260.1.51 | 1 / 0 | |
| 260.1.26 | 1 / 0 | |
| 260.1.25 | 1 / 0 | |
| 260.1.24 | 1 / 0 | |
| 260.1.23 | 1 / 0 | |
| 260.1.22 | 1 / 0 | |
| 260.1.21 | 1 / 0 | |
| 260.1.20 | 1 / 0 | |
| 260.1.19 | 1 / 0 | |
| 260.1.17 | 1 / 0 | |
| 260.1.16 | 1 / 0 | |
| 260.1.14 | 1 / 0 | |
| 260.1.13 | 1 / 0 | |
| 260.1.12 | 1 / 0 | |
| 260.1.11 | 1 / 0 | |
| 259.1.83 | 1 / 0 | |
| 259.1.82 | 1 / 0 | |
| 259.1.81 | 1 / 0 | |
| 259.1.80 | 1 / 0 | |
| 259.1.79 | 1 / 0 | |
| 259.1.78 | 1 / 0 | |
| 259.1.77 | 1 / 0 | |
| 259.1.76 | 1 / 0 | |
| 259.1.75 | 1 / 0 | |
| 259.1.74 | 1 / 0 | |
| 259.1.72 | 1 / 0 | |
| 259.1.71 | 1 / 0 | |
| 259.1.70 | 1 / 0 | |
| 259.1.69 | 1 / 0 | |
| 259.1.68 | 1 / 0 | |
| 259.1.67 | 1 / 0 | |
| 259.1.65 | 1 / 0 | |
| 259.1.64 | 1 / 0 | |
| 259.1.63 | 1 / 0 | |
| 259.1.61 | 1 / 0 | |
| 259.1.60 | 1 / 0 | |
| 259.1.59 | 1 / 0 | |
| 259.1.58 | 1 / 0 | |
| 259.1.57 | 1 / 0 | |
| 259.1.56 | 1 / 0 | |
| 259.1.55 | 1 / 0 | |
| 258.1.90 | 1 / 0 | |
| 258.1.89 | 1 / 0 | |
| 258.1.88 | 1 / 0 | |
| 258.1.86 | 1 / 0 | |
| 258.1.85 | 1 / 0 | |
| 258.1.84 | 1 / 0 | |
| 258.1.83 | 1 / 0 | |
| 258.1.82 | 1 / 0 |
v260.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v259.1.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v258.1.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v258.1.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v258.1.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v258.1.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v258.1.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v258.1.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v258.1.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v258.1.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.