@procore/core-icons
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/icons/Webhook.js | AI (source-diff): Generated React icon component with long SVG path data; consistent with this package's build output pattern. | ai | |
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): Google Code Prettify minified syntax highlighter bundled by Istanbul coverage reports; not malicious. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Large enterprise org with frequent team changes; publisher is the official procore-npm-bot with clean history. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine org churn for a large enterprise package; no takeover indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version gap (v11→v12) explains dormancy; publisher and repo are consistent with official Procore org. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon set package; 152 new files consistent with major version icon additions. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 12.18.0 | 0 / 35 | |
| 12.17.0 | 0 / 35 | |
| 12.16.0 | 0 / 35 | |
| 12.15.0 | 0 / 35 | |
| 12.14.0 | 0 / 35 | |
| 12.13.0 | 0 / 35 | |
| 12.12.0 | 0 / 35 | |
| 12.11.0 | 0 / 36 | |
| 12.10.1 | 0 / 36 | |
| 12.10.0 | 0 / 36 | |
| 12.9.1 | 0 / 36 | |
| 12.9.0 | 0 / 36 | |
| 12.8.0 | 0 / 35 | |
| 12.7.0 | 0 / 35 | |
| 12.6.1 | 0 / 35 | |
| 12.6.0 | 0 / 35 | |
| 12.5.0 | 0 / 35 | |
| 12.4.0 | 0 / 37 | |
| 11.0.5 | 0 / 29 |
v12.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.7.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.