@decaf-ts/db-decorators

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

tvenceslauvnogueira91pccostadcardosopdmfcdemersoncarvalho

Keywords

databasedecoratorsormrepositorytypescruddecaftypescripthookspersistencemodel

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:lib/validation/validation.cjs	AI (source-diff): Long line is a base64 sourcemap comment, not obfuscated logic; source is plain readable JS.	ai	2026/07/11
source-diff	obfuscated-file:lib/esm/validation/validation.js	AI (source-diff): Same sourcemap-comment false positive as the cjs counterpart.	ai	2026/07/11
maintainer-change	maintainer-added	AI (maintainer-change): Consistent with established publisher's org growth; no behavioral evidence of compromise.	ai	2026/07/11
source-diff	obfuscated-file:dist/esm/db-decorators.js	AI (source-diff): Bundled webpack output, not true obfuscation; matches build tooling in devDeps.	ai	2026/07/11
source-diff	obfuscated-file:dist/db-decorators.js	AI (source-diff): Bundled webpack output, not true obfuscation; matches build tooling in devDeps.	ai	2026/07/11
phantom-deps	phantom-dep:@decaf-ts/injectable-decorators	AI (phantom-deps): Same-org declared dep; used transitively or via decorators at runtime.	ai	2026/05/10
publish-pattern	dormant-publish	AI (publish-pattern): Publisher has 18 approved packages and 8 inbound edges; dormancy gap is plausible for a maintained OSS lib.	ai	2026/05/10
source-diff	obfuscated-file:lib/esm/model/overrides.js	AI (source-diff): Same pattern: inline sourcemap appended as base64 data URI causes long lines; actual code is readable and benign.	ai	2026/05/10
source-diff	obfuscated-file:lib/model/overrides.cjs	AI (source-diff): Long lines are inline sourcemaps (base64 data URI), not obfuscation; code is fully readable TypeScript compiled output.	ai	2026/05/10
phantom-deps	phantom-dep:better-docs	AI (phantom-deps): Doc tooling dependency referenced only in config files, not imported at runtime.	ai	2026/05/04
phantom-deps	phantom-dep:taffydb	AI (phantom-deps): Doc tooling dependency referenced only in config files, not imported at runtime.	ai	2026/05/04

Versions (showing 72 of 72)

Version	Deps	Published
0.8.15	4 / 1	2026-01-21
0.8.13	4 / 1	2026-01-10
0.8.7	4 / 1	2026-01-08
0.8.5	4 / 1	2026-01-08
0.7.4	3 / 2	2025-11-25
0.7.3	3 / 2	2025-11-25
0.7.2	3 / 2	2025-11-20
0.7.1	3 / 2	2025-11-20
0.7.0	3 / 2	2025-11-20
0.6.20	4 / 2	2025-11-07
0.6.19	4 / 2	2025-11-07
0.6.18	4 / 2	2025-11-07
0.6.17	4 / 2	2025-11-05
0.6.16	2 / 1	2025-11-05
0.6.15	2 / 1	2025-10-31
0.6.14	2 / 1	2025-10-31
0.6.13	0 / 1	2025-10-28
0.6.11	0 / 31	2025-10-15
0.6.10	0 / 31	2025-10-12
0.6.9	0 / 31	2025-09-23
0.6.8	0 / 31	2025-09-13
0.6.7	0 / 31	2025-09-13
0.6.6	0 / 31	2025-08-29
0.6.5	0 / 31	2025-08-25
0.6.4	0 / 31	2025-08-19
0.6.3	0 / 31	2025-07-28
0.6.2	0 / 31	2025-07-13
0.6.1	0 / 31	2025-05-27
0.6.0	0 / 31	2025-05-21
0.4.34	0 / 39	2025-04-21
0.4.33	0 / 39	2025-04-21
0.4.32	0 / 39	2025-04-21
0.4.31	0 / 35	2025-03-20
0.4.30	0 / 35	2025-03-20
0.4.29	0 / 35	2025-03-20
0.4.28	0 / 35	2025-03-20
0.4.27	0 / 35	2025-03-20
0.4.26	0 / 35	2025-02-22
0.4.25	0 / 35	2025-02-22
0.4.24	0 / 35	2025-02-22
0.4.23	0 / 35	2025-02-22
0.4.22	0 / 35	2025-02-22
0.4.21	0 / 35	2025-02-22
0.4.20	0 / 35	2025-02-22
0.4.19	0 / 35	2025-02-22
0.4.18	0 / 35	2024-11-11
0.4.17	0 / 35	2024-11-08
0.4.16	0 / 35	2024-11-08
0.4.13	0 / 35	2024-11-08
0.4.12	4 / 35	2024-11-08
0.4.11	4 / 35	2024-11-08
0.4.10	4 / 35	2024-11-08
0.4.9	4 / 35	2024-11-07
0.4.7	4 / 35	2024-11-07
0.4.6	4 / 35	2024-11-07
0.4.5	4 / 35	2024-11-07
0.4.4	0 / 35	2024-11-07
0.4.3	0 / 35	2024-10-30
0.4.2	0 / 35	2024-10-29
0.4.1	0 / 35	2024-10-25
0.4.0	0 / 35	2024-10-25
0.3.4	0 / 35	2024-10-22
0.3.1	0 / 35	2024-10-20
0.3.0	0 / 33	2024-10-20
0.2.0	0 / 31	2024-10-16
0.1.6	0 / 31	2024-10-11
0.1.5	0 / 31	2024-10-11
0.1.4	0 / 31	2024-10-11
0.1.3	0 / 31	2024-10-01
0.1.2	0 / 31	2024-10-01
0.1.1	0 / 31	2024-10-01
0.1.0	0 / 31	2024-09-30

v0.4.34

3 findings

HIGH New obfuscated file: dist/db-decorators.js 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: dist/esm/db-decorators.js 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.

v0.4.33

3 findings

HIGH New obfuscated file: dist/db-decorators.js 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: dist/esm/db-decorators.js 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.

v0.4.32

3 findings

HIGH New obfuscated file: dist/db-decorators.js 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: dist/esm/db-decorators.js 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.

v0.4.31

1 finding

LOW No provenance attestation provenance

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

v0.4.30

1 finding

LOW No provenance attestation provenance

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

v0.4.29

1 finding

LOW No provenance attestation provenance

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

v0.4.28

1 finding

LOW No provenance attestation provenance

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

v0.4.27

1 finding

LOW No provenance attestation provenance

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

v0.4.26

1 finding

LOW No provenance attestation provenance

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

v0.4.25

1 finding

LOW No provenance attestation provenance

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

v0.4.24

1 finding

LOW No provenance attestation provenance

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

v0.4.23

1 finding

LOW No provenance attestation provenance

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

v0.4.22

1 finding

LOW No provenance attestation provenance

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

v0.4.21

1 finding

LOW No provenance attestation provenance

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

v0.4.20

1 finding

LOW No provenance attestation provenance

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

v0.4.19

1 finding

LOW No provenance attestation provenance

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

v0.4.18

1 finding

LOW No provenance attestation provenance

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

v0.4.17

1 finding

LOW No provenance attestation provenance

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

v0.4.16

1 finding

LOW No provenance attestation provenance

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

v0.4.13

1 finding

LOW No provenance attestation provenance

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

v0.4.12

1 finding

LOW No provenance attestation provenance

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

v0.4.11

1 finding

LOW No provenance attestation provenance

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

v0.4.10

1 finding

LOW No provenance attestation provenance

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

v0.4.9

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

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.

v0.4.0

3 findings

HIGH New obfuscated file: lib/validation/validation.cjs 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: lib/esm/validation/validation.js 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.

v0.3.4

3 findings

HIGH New obfuscated file: lib/validation/validation.cjs 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: lib/esm/validation/validation.js 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.

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

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.