@procore/ai-translations
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Procore org package published via bot; no provenance is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:@procore/web-sdk-events | AI (phantom-deps): Declared dependency; used indirectly via same-org framework patterns. | ai | |
| phantom-deps | phantom-dep:use-sync-external-store | AI (phantom-deps): React hook library; use-sync-external-store is a peer-dependency pattern. | ai | |
| phantom-deps | phantom-dep:@types/use-sync-external-store | AI (phantom-deps): TypeScript types for declared dependency; loaded by convention. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Procore package; sparse README/keywords are normal for org-scoped libraries. | ai | |
| dependencies | unvetted-dep:@types/dom-chromium-ai | AI (dependencies): Type-definition-only package for browser AI APIs; no runtime risk, stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/dom-chromium-ai | AI (phantom-deps): Type-only package; not directly imported by convention — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@procore/web-sdk-storage | AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 6 / 23 | |
| 0.6.2 | 6 / 23 | |
| 0.6.1 | 6 / 23 | |
| 0.6.0 | 6 / 23 | |
| 0.5.0 | 6 / 23 | |
| 0.4.0 | 6 / 23 | |
| 0.3.0 | 6 / 23 | |
| 0.2.0 | 6 / 22 | |
| 0.1.0 | 4 / 11 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.