← Home

@justeattakeaway/pie-monorepo-utils

npm Repository Homepage

Scripts and utilities used by the PIE monorepo

8
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mwh1989anastasiia.horbanashleynolanjamieomaguirelizzie.turneydavidpn.11roberto.santanammakwe-onyekafozzie-botmaledr5

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@justeattakeaway/eslint-plugin-snacks-pie-migration AI (phantom-deps): Same-org eslint plugin declared as runtime dep; may be used indirectly via config resolution rather than direct import. ai
semgrep semgrep:child-process-import AI (semgrep): CLI build tool legitimately uses execSync for monorepo version detection; stable pattern for this package. ai
bogus-package bogus-package AI (bogus-package): Internal monorepo tooling; sparse README/keywords expected for org-internal packages. ai

Versions (showing 8 of 8)

Version Deps Published
0.9.3 3 / 1
0.9.2 3 / 0
0.9.1 3 / 0
0.9.0 2 / 0
0.8.0 2 / 0
0.7.0 2 / 0
0.6.0 2 / 0
0.5.1 0 / 0

v0.9.3

1 finding
LOW No provenance attestation provenance

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

v0.9.2

1 finding
LOW No provenance attestation provenance

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

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

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.