@dbml/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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @dbml/core is the core module of the DBML ecosystem under the @dbml scope — not a typosquat of 'cors'. The match is a false positive driven purely by edit distance on the unscoped portion. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): luxon is declared in package.json dependencies and bundled via Vite; indirect import pattern is expected for this build setup. | ai | |
| phantom-deps | phantom-dep:antlr4 | AI (phantom-deps): antlr4 is declared in package.json dependencies and used in the parser build step; indirect import pattern is expected. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is declared in package.json dependencies; indirect import pattern is expected for a Vite-bundled library. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is declared in package.json dependencies; indirect import pattern is expected for a Vite-bundled library. | ai | |
| phantom-deps | phantom-dep:parsimmon | AI (phantom-deps): parsimmon is declared in package.json dependencies and used in the deprecated parser build; indirect import pattern is expected. | ai | |
| phantom-deps | phantom-dep:pluralize | AI (phantom-deps): pluralize is declared in package.json dependencies; indirect import pattern is expected for a Vite-bundled library. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.2.5 | 7 / 1 | |
| 8.2.4 | 7 / 1 | |
| 8.2.3 | 7 / 1 | |
| 8.2.2 | 7 / 1 | |
| 8.2.1 | 7 / 1 | |
| 8.2.0 | 7 / 1 | |
| 8.1.0 | 7 / 1 | |
| 8.0.0 | 7 / 1 | |
| 7.1.1 | 7 / 1 |
v8.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
2 findingsPackage name '@dbml/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.