@dereekb/dbx-form — Greenflagged

@dereekb/dbx-form =======

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

dereekb

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:@ngx-formly/material	AI (npm-metadata): Publisher's own fork pinned to a specific commit; stable pattern across this package's versions.	ai	2026/05/31
npm-metadata	url-dep:@ngx-formly/core	AI (npm-metadata): Publisher's own fork pinned to a specific commit; stable pattern across this package's versions.	ai	2026/05/31
npm-metadata	url-dep:ngx-mapbox-gl	AI (npm-metadata): Publisher's own fork pinned to a specific commit; stable pattern across this package's versions.	ai	2026/05/31
source-diff	obfuscated-file:fesm2022/dereekb-dbx-form-expand.field.component-xIW9lckC.mjs	AI (source-diff): Standard Angular fesm2022 compiled output; long lines are normal for Angular compiler bundles, not obfuscation.	ai	2026/05/06
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dependency; not directly imported in source.	ai	2026/05/03
source-diff	obfuscated-file:fesm2022/dereekb-dbx-form-quiz.mjs	AI (source-diff): Standard Angular FESM2022 bundle output; long lines are normal for bundled Angular libraries.	ai	2026/05/03
source-diff	obfuscated-file:types/dereekb-dbx-form.d.ts	AI (source-diff): Angular compiled .d.ts files have long lines due to type exports; not obfuscation.	ai	2026/05/03
source-diff	obfuscated-file:fesm2022/dereekb-dbx-form-formfield.field.component-BQyujXe3.mjs	AI (source-diff): Standard Angular FESM2022 bundle output; long lines are Angular component metadata, not obfuscation.	ai	2026/04/30
source-diff	obfuscated-file:fesm2022/dereekb-dbx-form-array.field.component-1wYSd4d3.mjs	AI (source-diff): Standard Angular FESM2022 bundle output; long lines are Angular component metadata, not obfuscation.	ai	2026/04/30
source-diff	obfuscated-file:fesm2022/dereekb-dbx-form-expand.field.component-Bp5_uO1A.mjs	AI (source-diff): Angular FESM2022 bundle with readable code; long lines are standard Angular compiler output, not obfuscation.	ai	2026/04/30

Versions (showing 51 of 107)

View all versions

Version	Deps	Published
13.15.0	1 / 0	2026-06-05
13.14.0	1 / 0	2026-06-03
13.13.0	1 / 0	2026-06-02
13.12.9	1 / 0	2026-05-31
13.12.8	1 / 0	2026-05-30
13.12.7	1 / 0	2026-05-29
13.12.6	1 / 0	2026-05-29
13.12.5	1 / 0	2026-05-29
13.12.4	1 / 0	2026-05-28
13.12.3	1 / 0	2026-05-27
13.12.2	1 / 0	2026-05-27
13.12.1	1 / 0	2026-05-27
13.12.0	1 / 0	2026-05-26
13.11.18	1 / 0	2026-05-21
13.11.17	1 / 0	2026-05-19
13.11.16	1 / 0	2026-05-19
13.11.15	1 / 0	2026-05-18
13.11.14	1 / 0	2026-05-17
13.11.13	1 / 0	2026-05-16
13.11.12	1 / 0	2026-05-15
13.11.11	1 / 0	2026-05-15
13.11.10	1 / 0	2026-05-12
13.11.9	1 / 0	2026-05-11
13.11.8	1 / 0	2026-05-11
13.11.7	1 / 0	2026-05-11
13.11.6	1 / 0	2026-05-10
13.11.5	1 / 0	2026-05-10
13.11.4	1 / 0	2026-05-09
13.11.3	1 / 0	2026-05-08
13.11.2	1 / 0	2026-05-07
13.11.1	1 / 0	2026-05-07
13.11.0	1 / 0	2026-05-07
13.10.9	1 / 0	2026-05-05
13.10.8	1 / 0	2026-05-05
13.10.7	1 / 0	2026-05-04
13.10.6	1 / 0	2026-05-02
13.10.5	1 / 0	2026-05-01
13.10.4	1 / 0	2026-05-01
13.10.3	1 / 0	2026-04-30
13.10.2	1 / 0	2026-04-29
13.10.1	1 / 0	2026-04-28
13.10.0	1 / 0	2026-04-27
13.9.0	1 / 0	2026-04-23
13.8.0	1 / 0	2026-04-11
13.7.0	1 / 0	2026-04-09
13.6.17	1 / 0	2026-04-08
13.6.16	1 / 0	2026-04-03
13.6.15	1 / 0	2026-04-03
13.6.14	1 / 0	2026-04-02
13.6.13	1 / 0	2026-04-01
13.6.12	1 / 0	2026-04-01

v13.15.0

1 finding

LOW No provenance attestation provenance

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

v13.14.0

1 finding

LOW No provenance attestation provenance

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

v13.13.0

1 finding

LOW No provenance attestation provenance

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

v13.12.9

1 finding

LOW No provenance attestation provenance

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

v13.12.8

1 finding

LOW No provenance attestation provenance

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

v13.12.7

1 finding

LOW No provenance attestation provenance

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

v13.12.6

1 finding

LOW No provenance attestation provenance

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

v13.12.5

1 finding

LOW No provenance attestation provenance

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

v13.12.4

1 finding

LOW No provenance attestation provenance

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

v13.12.3

1 finding

LOW No provenance attestation provenance

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

v13.12.2

1 finding

LOW No provenance attestation provenance

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

v13.12.1

1 finding

LOW No provenance attestation provenance

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

v13.12.0

1 finding

LOW No provenance attestation provenance

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

v13.11.18

1 finding

LOW No provenance attestation provenance

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

v13.11.17

1 finding

LOW No provenance attestation provenance

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

v13.11.16

1 finding

LOW No provenance attestation provenance

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

v13.11.15

1 finding

LOW No provenance attestation provenance

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

v13.11.14

1 finding

LOW No provenance attestation provenance

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

v13.11.13

1 finding

LOW No provenance attestation provenance

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

v13.11.12

1 finding

LOW No provenance attestation provenance

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

v13.11.11

1 finding

LOW No provenance attestation provenance

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

v13.11.10

1 finding

LOW No provenance attestation provenance

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

v13.11.9

1 finding

LOW No provenance attestation provenance

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

v13.11.8

1 finding

LOW No provenance attestation provenance

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

v13.11.7

1 finding

LOW No provenance attestation provenance

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

v13.11.6

1 finding

LOW No provenance attestation provenance

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

v13.11.5

1 finding

LOW No provenance attestation provenance

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

v13.11.4

1 finding

LOW No provenance attestation provenance

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

v13.11.3

1 finding

LOW No provenance attestation provenance

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

v13.11.2

1 finding

LOW No provenance attestation provenance

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

v13.11.1

1 finding

LOW No provenance attestation provenance

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

v13.11.0

1 finding

LOW No provenance attestation provenance

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

v13.10.9

2 findings

HIGH New obfuscated file: fesm2022/dereekb-dbx-form-expand.field.component-xIW9lckC.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.

v13.10.8

2 findings

HIGH New obfuscated file: fesm2022/dereekb-dbx-form-expand.field.component-xIW9lckC.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.

v13.10.7

1 finding

LOW No provenance attestation provenance

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

v13.10.6

1 finding

LOW No provenance attestation provenance

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

v13.10.5

1 finding

LOW No provenance attestation provenance

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

v13.10.4

1 finding

LOW No provenance attestation provenance

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

v13.10.3

1 finding

LOW No provenance attestation provenance

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

v13.10.2

1 finding

LOW No provenance attestation provenance

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

v13.10.0

2 findings

HIGH New obfuscated file: fesm2022/dereekb-dbx-form-expand.field.component-Bp5_uO1A.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.

v13.9.0

2 findings

HIGH New obfuscated file: fesm2022/dereekb-dbx-form-expand.field.component-Bp5_uO1A.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.

v13.8.0

4 findings

HIGH New obfuscated file: fesm2022/dereekb-dbx-form-array.field.component-1wYSd4d3.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.

HIGH New obfuscated file: fesm2022/dereekb-dbx-form-expand.field.component-Bp5_uO1A.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.

HIGH New obfuscated file: fesm2022/dereekb-dbx-form-formfield.field.component-BQyujXe3.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.

v13.7.0

1 finding

LOW No provenance attestation provenance

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

v13.6.17

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.

v13.6.16

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.

v13.6.15

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.

v13.6.14

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.

v13.6.13

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.

v13.6.12

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.