@dereekb/dbx-core
@dereekb/dbx-core =======
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:types/dereekb-dbx-core.d.ts | AI (source-diff): File is a bundled TypeScript declaration rollup (.d.ts); long lines are normal for Angular library type exports. | ai | |
| source-diff | obfuscated-file:esm2022/lib/rxjs/lockset.mjs | AI (source-diff): Angular compiler ESM2022 output with long metadata lines; not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/lib/rxjs/rxjs.directive.mjs | AI (source-diff): Angular compiler ESM2022 output with long metadata lines; not obfuscation. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard Angular/TypeScript runtime dep; implicit usage is expected. | ai |
Versions (showing 51 of 107)
| Version | Deps | Published |
|---|---|---|
| 13.15.0 | 1 / 0 | |
| 13.14.0 | 1 / 0 | |
| 13.13.0 | 1 / 0 | |
| 13.12.9 | 1 / 0 | |
| 13.12.8 | 1 / 0 | |
| 13.12.7 | 1 / 0 | |
| 13.12.6 | 1 / 0 | |
| 13.12.5 | 1 / 0 | |
| 13.12.4 | 1 / 0 | |
| 13.12.3 | 1 / 0 | |
| 13.12.2 | 1 / 0 | |
| 13.12.1 | 1 / 0 | |
| 13.12.0 | 1 / 0 | |
| 13.11.18 | 1 / 0 | |
| 13.11.17 | 1 / 0 | |
| 13.11.15 | 1 / 0 | |
| 13.11.14 | 1 / 0 | |
| 13.11.13 | 1 / 0 | |
| 13.11.12 | 1 / 0 | |
| 13.11.11 | 1 / 0 | |
| 13.11.10 | 1 / 0 | |
| 13.11.9 | 1 / 0 | |
| 13.11.8 | 1 / 0 | |
| 13.11.7 | 1 / 0 | |
| 13.11.6 | 1 / 0 | |
| 13.11.5 | 1 / 0 | |
| 13.11.4 | 1 / 0 | |
| 13.11.3 | 1 / 0 | |
| 13.11.2 | 1 / 0 | |
| 13.11.1 | 1 / 0 | |
| 13.11.0 | 1 / 0 | |
| 13.10.9 | 1 / 0 | |
| 13.10.8 | 1 / 0 | |
| 13.10.7 | 1 / 0 | |
| 13.10.6 | 1 / 0 | |
| 13.10.5 | 1 / 0 | |
| 13.10.4 | 1 / 0 | |
| 13.10.3 | 1 / 0 | |
| 13.10.2 | 1 / 0 | |
| 13.10.1 | 1 / 0 | |
| 13.10.0 | 1 / 0 | |
| 13.9.0 | 1 / 0 | |
| 13.8.0 | 1 / 0 | |
| 13.7.0 | 1 / 0 | |
| 13.6.17 | 1 / 0 | |
| 13.6.16 | 1 / 0 | |
| 13.6.15 | 1 / 0 | |
| 13.6.14 | 1 / 0 | |
| 13.6.13 | 1 / 0 | |
| 13.6.12 | 1 / 0 | |
| 13.6.11 | 1 / 0 |
v13.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.