← Home

@colijnit/catalog

npm Repository Homepage
31
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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/lib/component/base/article-base.component.js AI (source-diff): Angular ng-packagr build output, readable source, not true obfuscation. ai
source-diff large-new-source-files AI (source-diff): Expected due to diff against much older imported sibling version. ai
source-diff source-size-tripled AI (source-diff): Bundled dictionaries/build artifacts inflate size; not injected payload. ai
source-diff obfuscated-file:fesm2022/colijnit-catalog.mjs AI (source-diff): Angular fesm2022 bundled build output, not obfuscation. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a standard implicit Angular runtime dep. ai

Versions (showing 31 of 31)

Version Deps Published
300.1.1 1 / 0
300.1.0 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.9 1 / 0
261.20.8 1 / 0
261.20.7 1 / 0
261.20.6 1 / 0
261.20.5 1 / 0
261.20.4 1 / 0
261.20.3 1 / 0
261.20.2 1 / 0
261.20.1 1 / 0
261.20.0 1 / 0
261.1.0 1 / 0
260.1.6 1 / 0
260.1.5 1 / 0
260.1.4 1 / 0
260.1.3 1 / 0
260.1.2 1 / 0
259.1.8 1 / 0
259.1.7 1 / 0
258.1.11 1 / 0
258.1.10 1 / 0
258.1.9 1 / 0

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 → patrickvkeulen (on 2026-07-24, known maintainer) provenance

This version was published by a different npm account (patrickvkeulen) than the most recent previously approved version (ralf.eversen) on 2026-07-24, 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.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: deyan_colijnit → ralf.eversen (on 2026-07-13, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v261.20.5

3 findings
HIGH New obfuscated file: fesm2022/colijnit-catalog.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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-03-27, known maintainer) provenance

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

3 findings
HIGH New obfuscated file: fesm2022/colijnit-catalog.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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-03-10, known maintainer) provenance

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

3 findings
HIGH New obfuscated file: fesm2022/colijnit-catalog.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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-03-04, known maintainer) provenance

This version was published by a different npm account (elske) than the most recent previously approved version (ralf.eversen) on 2026-03-04, 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.2

3 findings
HIGH New obfuscated file: fesm2022/colijnit-catalog.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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-03-02, known maintainer) provenance

This version was published by a different npm account (elske) than the most recent previously approved version (ralf.eversen) on 2026-03-02, 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.1

3 findings
HIGH New obfuscated file: fesm2022/colijnit-catalog.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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 → goran_silic_colijn (on 2026-02-18, known maintainer) provenance

This version was published by a different npm account (goran_silic_colijn) than the most recent previously approved version (ralf.eversen) on 2026-02-18, 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.20.0

2 findings
HIGH New obfuscated file: fesm2022/colijnit-catalog.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v261.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: patrickvkeulen → ralf.eversen (on 2026-01-13, known maintainer) provenance

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

v260.1.5

1 finding
LOW No provenance attestation provenance

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

v260.1.4

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-03-02, known maintainer) provenance

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

v260.1.3

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: jilliscit → patrickvkeulen (on 2025-12-17, known maintainer) provenance

This version was published by a different npm account (patrickvkeulen) than the most recent previously approved version (jilliscit) on 2025-12-17, 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.

v260.1.2

1 finding
LOW No provenance attestation provenance

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

v259.1.8

1 finding
LOW No provenance attestation provenance

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

v259.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v258.1.11

1 finding
LOW No provenance attestation provenance

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

v258.1.10

1 finding
LOW No provenance attestation provenance

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

v258.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.