← Home

hjson

npm Repository Homepage
9
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

dqsullylaktak

Keywords

jsoncommentsconfighjsonparserserializerhuman

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed-stale AI (provenance): 2018 maintainer transfer, stable on npm for years; not a takeover pattern. ai
publish-pattern dormant-publish AI (publish-pattern): Long-lived stable package with sparse release cadence; no malicious content. ai

Versions (showing 9 of 9)

Version Deps Published
3.2.2 0 / 4
3.2.1 0 / 4
3.2.0 0 / 4
3.1.2 0 / 4
3.1.1 0 / 4
3.1.0 0 / 4
3.0.2 0 / 4
3.0.1 0 / 4
3.0.0 0 / 4

v3.2.1

2 findings
MEDIUM Publisher changed: laktak → dqsully (on 2019-10-22, unremoved on npm for 2462d) provenance

This version was published by a different npm account (dqsully) than the most recent previously approved version (laktak) on 2019-10-22. It has since remained available on npm for 2462 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v3.2.0

2 findings
MEDIUM Publisher changed: laktak → dqsully (on 2019-10-07, unremoved on npm for 2477d) provenance

This version was published by a different npm account (dqsully) than the most recent previously approved version (laktak) on 2019-10-07. It has since remained available on npm for 2477 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v3.1.2

2 findings
MEDIUM Publisher changed: laktak → dqsully (on 2018-11-13, unremoved on npm for 2805d) provenance

This version was published by a different npm account (dqsully) than the most recent previously approved version (laktak) on 2018-11-13. It has since remained available on npm for 2805 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

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

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