@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 7 of 110)
| Version | Deps | Published |
|---|---|---|
| 12.6.1 | 1 / 0 | |
| 12.6.0 | 1 / 0 | |
| 12.5.10 | 1 / 0 | |
| 12.5.9 | 1 / 0 | |
| 12.5.8 | 1 / 0 | |
| 12.5.7 | 1 / 0 | |
| 12.5.6 | 1 / 0 |
v12.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.