@procore/core-scripts
A CLI to enhance your development experience
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jest | AI (phantom-deps): Build-tooling CLI; jest declared as config-level dep, not directly imported by design. | ai | |
| phantom-deps | phantom-dep:sass | AI (phantom-deps): Config-level dep for webpack sass-loader integration; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Config-level dep; expected for a webpack build-tooling CLI. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Config-level dep; expected for a build-tooling CLI. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Config-level dep; expected for a linting/formatting CLI. | ai | |
| phantom-deps | phantom-dep:terser | AI (phantom-deps): Config-level dep; expected for a webpack build-tooling CLI. | ai | |
| phantom-deps | phantom-dep:browserslist | AI (phantom-deps): Config-level dep; expected for a build-tooling CLI. | ai | |
| phantom-deps | phantom-dep:@procore/eslint-config | AI (phantom-deps): Same-org eslint config; declared as peer/config dep, not directly imported. | ai | |
| phantom-deps | phantom-dep:stylelint-prettier | AI (phantom-deps): Config-level stylelint plugin; expected for a linting CLI. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 12.5.0 | 111 / 26 | |
| 12.4.2 | 111 / 26 | |
| 12.4.1 | 111 / 26 | |
| 12.4.0 | 111 / 26 | |
| 12.3.1 | 111 / 26 |
v12.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.