← Home

ddata

ddata

14
Versions
MIT
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

75lb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): ddata 0.0.0 is a legitimate initial release from a trusted publisher (75lb) with 4230+ days of history and 33 subsequent versions. The 0.0.0 version is a known placeholder pattern, not malicious. ai
publish-pattern new-deps-added AI (publish-pattern): handlebars is a well-known templating library appropriate for this jsdoc/markdown helper package; the swap from boil to handlebars is a legitimate refactor. ai
dependencies unvetted-dep:handlebars AI (dependencies): handlebars is a widely-used, established templating library; its use here is contextually appropriate for a documentation template package. ai
phantom-deps phantom-dep:object-tools AI (phantom-deps): object-tools is listed in dependencies and referenced in config; low-risk phantom-dep finding for this package. ai
provenance no-provenance AI (provenance): Established package from a trusted publisher with a long history; lack of Sigstore provenance is expected for packages predating that tooling. ai
bogus-package bogus-package AI (bogus-package): ddata is a legitimate jsdoc2md ecosystem helper package; sparse metadata is a cosmetic issue, not indicative of spam or malicious intent. ai

Versions (showing 14 of 14)

Version Deps Published
0.2.0 5 / 1
0.1.28 8 / 1
0.1.26 8 / 1
0.1.17 5 / 1
0.1.16 5 / 1
0.1.15 5 / 1
0.1.14 5 / 1
0.1.13 5 / 1
0.1.12 5 / 1
0.1.11 5 / 1
0.1.9 5 / 2
0.1.4 5 / 2
0.1.1 5 / 2
0.0.0 0 / 0

v0.2.0

1 finding
INFO No provenance attestation provenance

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

v0.1.28

1 finding
LOW No provenance attestation provenance

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

v0.1.26

1 finding
INFO No provenance attestation provenance

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

v0.1.17

1 finding
INFO No provenance attestation provenance

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

v0.1.16

1 finding
INFO No provenance attestation provenance

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

v0.1.15

1 finding
INFO No provenance attestation provenance

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

v0.1.14

1 finding
INFO No provenance attestation provenance

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

v0.1.13

1 finding
INFO No provenance attestation provenance

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

v0.1.12

1 finding
INFO No provenance attestation provenance

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

v0.1.11

1 finding
INFO No provenance attestation provenance

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

v0.1.9

1 finding
INFO No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.