@justeattakeaway/pie-monorepo-utils
Scripts and utilities used by the PIE monorepo
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.9.7 | 3 / 1 | |
| 0.9.6 | 3 / 1 | |
| 0.9.5 | 3 / 1 | |
| 0.9.4 | 3 / 1 | |
| 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 | |
| 0.5.0 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.3.1 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.