← Home

@dbml/parse

npm Repository Homepage

DBML parser v2

25
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

phuongduyphanthi.nguyenphucnguyen101nguyen.hoanghuyleminh01thonx-holisticshuy-dna

Keywords

dbmldbml-parse

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:parcel AI (typosquat): @dbml/parse is a scoped DBML parser in the established @dbml namespace by Holistics; the Levenshtein match to 'parcel' is a false positive with no impersonation intent. ai
phantom-deps phantom-dep:luxon AI (phantom-deps): luxon is a declared runtime dependency; bundled via Vite, so static import tracing may not detect usage. Legitimate dependency for this package. ai
phantom-deps phantom-dep:lodash-es AI (phantom-deps): lodash-es is a declared runtime dependency; bundled via Vite, so static import tracing may not detect usage. Legitimate dependency for this package. ai

Versions (showing 25 of 25)

Version Deps Published
8.2.5 3 / 2
8.2.4 3 / 2
8.2.3 3 / 2
8.2.2 3 / 2
8.2.1 3 / 2
8.2.0 3 / 2
8.1.0 3 / 2
8.0.0 3 / 2
7.1.1 2 / 2
7.1.0 2 / 2
7.0.0 2 / 2
6.6.0 2 / 2
6.4.0 2 / 2
6.3.0 2 / 2
6.2.1 1 / 1
6.2.0 1 / 1
6.1.0 1 / 11
6.0.0 1 / 11
5.5.1 1 / 11
5.5.0 1 / 11
5.4.1 1 / 11
5.3.0 1 / 12
5.2.0 1 / 12
5.1.0 1 / 9
5.0.0 1 / 9

v8.2.5

1 finding
LOW No provenance attestation provenance

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

v8.2.4

1 finding
LOW No provenance attestation provenance

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

v8.2.3

1 finding
LOW No provenance attestation provenance

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

v8.2.2

1 finding
LOW No provenance attestation provenance

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

v8.2.1

1 finding
LOW No provenance attestation provenance

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

v8.2.0

1 finding
LOW No provenance attestation provenance

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

v8.1.0

1 finding
LOW No provenance attestation provenance

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

v8.0.0

1 finding
LOW No provenance attestation provenance

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

v7.1.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.

v7.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.

v7.0.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.

v6.6.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.