← Home

@mkven/samples-generation

npm Repository Homepage

Generate sample data for PostgreSQL, ClickHouse, SQLite, and Trino with a unified interface

9
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

tebuchetdmyaro

Keywords

data-generationsample-datatest-datapostgresqlclickhousesqlitetrinodatabasefakermock-data

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:@mkven/name-dictionaries AI (npm-metadata): Same-org GitHub dependency; consistent pattern across this package family, not a registry bypass attack. ai
phantom-deps phantom-dep:@mkven/name-dictionaries AI (phantom-deps): Same-org scoped dep; likely used transitively or in bundled dist output, not a real phantom. ai

Versions (showing 9 of 9)

Version Deps Published
0.6.0 6 / 10
0.5.2 6 / 10
0.5.1 6 / 9
0.5.0 6 / 9
0.4.1 6 / 13
0.4.0 6 / 13
0.3.0 6 / 13
0.2.0 6 / 13
0.1.0 6 / 11

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.2

1 finding
LOW No provenance attestation provenance

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

v0.5.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.

v0.5.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tebuchet.

LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.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.

v0.2.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.

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