@decaf-ts/db-decorators
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
Keywords
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 | |
| source-diff | obfuscated-file:lib/esm/validation/validation.js | AI (source-diff): Same sourcemap-comment false positive as the cjs counterpart. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with established publisher's org growth; no behavioral evidence of compromise. | ai | |
| source-diff | obfuscated-file:dist/esm/db-decorators.js | AI (source-diff): Bundled webpack output, not true obfuscation; matches build tooling in devDeps. | ai | |
| source-diff | obfuscated-file:dist/db-decorators.js | AI (source-diff): Bundled webpack output, not true obfuscation; matches build tooling in devDeps. | ai | |
| phantom-deps | phantom-dep:@decaf-ts/injectable-decorators | AI (phantom-deps): Same-org declared dep; used transitively or via decorators at runtime. | ai | |
| 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 | |
| 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 | |
| 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 | |
| phantom-deps | phantom-dep:better-docs | AI (phantom-deps): Doc tooling dependency referenced only in config files, not imported at runtime. | ai | |
| phantom-deps | phantom-dep:taffydb | AI (phantom-deps): Doc tooling dependency referenced only in config files, not imported at runtime. | ai |
Versions (showing 51 of 72)
| Version | Deps | Published |
|---|---|---|
| 0.8.15 | 4 / 1 | |
| 0.8.13 | 4 / 1 | |
| 0.8.7 | 4 / 1 | |
| 0.8.5 | 4 / 1 | |
| 0.7.4 | 3 / 2 | |
| 0.7.3 | 3 / 2 | |
| 0.7.2 | 3 / 2 | |
| 0.7.1 | 3 / 2 | |
| 0.7.0 | 3 / 2 | |
| 0.6.20 | 4 / 2 | |
| 0.6.19 | 4 / 2 | |
| 0.6.18 | 4 / 2 | |
| 0.6.17 | 4 / 2 | |
| 0.6.16 | 2 / 1 | |
| 0.6.15 | 2 / 1 | |
| 0.6.14 | 2 / 1 | |
| 0.6.13 | 0 / 1 | |
| 0.6.11 | 0 / 31 | |
| 0.6.10 | 0 / 31 | |
| 0.6.9 | 0 / 31 | |
| 0.6.8 | 0 / 31 | |
| 0.6.7 | 0 / 31 | |
| 0.6.6 | 0 / 31 | |
| 0.6.5 | 0 / 31 | |
| 0.6.4 | 0 / 31 | |
| 0.6.3 | 0 / 31 | |
| 0.6.2 | 0 / 31 | |
| 0.6.1 | 0 / 31 | |
| 0.6.0 | 0 / 31 | |
| 0.4.34 | 0 / 39 | |
| 0.4.33 | 0 / 39 | |
| 0.4.32 | 0 / 39 | |
| 0.4.31 | 0 / 35 | |
| 0.4.30 | 0 / 35 | |
| 0.4.29 | 0 / 35 | |
| 0.4.28 | 0 / 35 | |
| 0.4.27 | 0 / 35 | |
| 0.4.26 | 0 / 35 | |
| 0.4.25 | 0 / 35 | |
| 0.4.24 | 0 / 35 | |
| 0.4.23 | 0 / 35 | |
| 0.4.22 | 0 / 35 | |
| 0.4.21 | 0 / 35 | |
| 0.4.20 | 0 / 35 | |
| 0.4.19 | 0 / 35 | |
| 0.4.18 | 0 / 35 | |
| 0.4.17 | 0 / 35 | |
| 0.4.16 | 0 / 35 | |
| 0.4.13 | 0 / 35 | |
| 0.4.12 | 4 / 35 | |
| 0.4.11 | 4 / 35 |
v0.4.34
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.32
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.