← Home

backfill-hasher

npm Repository Homepage

Backfill Hasher

47
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

microsoft1esmicrosoft-oss-releaseskenotronkenotron_msftvincentbaillybweggersenecraig12345_msft

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:fs-extra AI (phantom-deps): fs-extra is a declared runtime dependency; phantom-dep heuristic misfires on this package. ai
phantom-deps phantom-dep:backfill-config AI (phantom-deps): backfill-config is a declared runtime dependency; phantom-dep heuristic misfires on this package. ai
provenance publisher-changed AI (provenance): Microsoft/lage repo publishes via GitHub Actions with SLSA attestation; CI publisher transition is expected and verified. ai
semgrep semgrep:dynamic-require AI (semgrep): The dynamic require loads a package.json from a known filesystem path — standard pattern for a build-cache hasher. No arbitrary code execution risk. ai

Versions (showing 47 of 47)

Version Deps Published
6.7.12 2 / 2
6.7.11 2 / 2
6.7.10 2 / 2
6.7.9 2 / 2
6.7.8 2 / 2
6.7.7 2 / 2
6.7.6 2 / 2
6.7.5 2 / 2
6.7.4 2 / 2
6.7.3 2 / 2
6.7.2 2 / 2
6.7.1 2 / 2
6.7.0 2 / 6
6.6.3 5 / 7
6.6.2 5 / 7
6.6.1 5 / 7
6.6.0 5 / 7
6.5.3 5 / 7
6.5.2 5 / 7
6.5.1 5 / 7
6.5.0 6 / 7
6.4.5 6 / 7
6.4.4 6 / 7
6.4.3 6 / 7
6.4.2 6 / 7
6.4.1 6 / 7
6.4.0 6 / 7
6.3.1 6 / 7
6.3.0 6 / 7
6.2.9 6 / 7
6.2.8 6 / 7
6.2.7 6 / 7
6.2.6 6 / 7
6.2.5 6 / 7
6.2.4 6 / 7
6.2.3 6 / 7
6.2.2 6 / 7
6.2.1 6 / 7
6.2.0 6 / 7
6.1.5 6 / 7
6.1.4 6 / 7
6.1.3 6 / 7
6.1.2 6 / 6
6.1.1 6 / 6
6.1.0 6 / 6
6.0.1 6 / 6
6.0.0 6 / 6

v6.7.12

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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.

v6.5.3

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

1 finding
LOW No provenance attestation provenance

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

v6.5.1

1 finding
LOW No provenance attestation provenance

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

v6.5.0

2 findings
MEDIUM Publisher changed: kenotron_msft → ecraig12345_msft (on 2023-09-05, unremoved on npm for 1049d) provenance

This version was published by a different npm account (ecraig12345_msft) than the most recent previously approved version (kenotron_msft) on 2023-09-05. It has since remained available on npm for 1049 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.

v6.4.5

1 finding
LOW No provenance attestation provenance

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

v6.4.4

1 finding
LOW No provenance attestation provenance

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

v6.4.3

1 finding
LOW No provenance attestation provenance

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

v6.4.2

1 finding
LOW No provenance attestation provenance

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

v6.4.1

1 finding
LOW No provenance attestation provenance

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

v6.4.0

1 finding
LOW No provenance attestation provenance

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

v6.3.1

1 finding
LOW No provenance attestation provenance

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

v6.3.0

1 finding
LOW No provenance attestation provenance

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

v6.2.9

1 finding
LOW No provenance attestation provenance

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

v6.2.8

1 finding
LOW No provenance attestation provenance

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

v6.2.7

1 finding
LOW No provenance attestation provenance

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

v6.2.6

1 finding
LOW No provenance attestation provenance

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

v6.2.5

1 finding
LOW No provenance attestation provenance

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

v6.2.4

1 finding
LOW No provenance attestation provenance

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

v6.2.3

1 finding
LOW No provenance attestation provenance

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

v6.2.2

1 finding
LOW No provenance attestation provenance

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

v6.2.1

1 finding
LOW No provenance attestation provenance

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

v6.2.0

1 finding
LOW No provenance attestation provenance

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

v6.1.5

1 finding
LOW No provenance attestation provenance

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

v6.1.4

1 finding
LOW No provenance attestation provenance

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

v6.1.3

1 finding
LOW No provenance attestation provenance

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

v6.1.2

1 finding
LOW No provenance attestation provenance

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

v6.1.1

1 finding
LOW No provenance attestation provenance

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

v6.1.0

1 finding
LOW No provenance attestation provenance

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

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

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