← Home

@joggr/config

npm Repository Homepage

Configuration SDK for Joggr - supports TypeScript, JSON, JSONC, and YAML config files

4
Versions
SEE LICENSE IN LICENSE.md
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

zrosenbauerdanielbot

Keywords

c12configconfigurationjoggrtypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): es-toolkit is a well-known utility library; addition is a routine dependency swap, not a suspicious new dep. ai
phantom-deps phantom-dep:zod-to-json-schema AI (phantom-deps): zod-to-json-schema is used in the build/schema generation script, not directly imported at runtime. This is a stable pattern for this package's schema generation workflow. ai

Versions (showing 4 of 4)

Version Deps Published
0.3.5 3 / 7
0.3.2 4 / 6
0.2.0 3 / 6
0.1.0 3 / 6

v0.3.5

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: GitHub Actions.

LOW No provenance attestation provenance

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

v0.3.2

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.