@procore/core-react
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash.uniq | AI (phantom-deps): Lodash utilities declared as deps for downstream consumers; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Same pattern — declared for consumer use, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:lodash.times | AI (phantom-deps): Same pattern — declared for consumer use, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:lodash.groupby | AI (phantom-deps): Same pattern — declared for consumer use, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@atlaskit/pragmatic-drag-and-drop | AI (phantom-deps): Atlaskit DnD dep declared for consumers; stable false positive for this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 12.52.0 | 36 / 74 | |
| 12.51.0 | 36 / 74 | |
| 12.50.1 | 35 / 74 | |
| 12.50.0 | 35 / 74 | |
| 12.49.1 | 35 / 74 | |
| 12.49.0 | 35 / 74 | |
| 12.48.2 | 35 / 74 | |
| 12.48.1 | 35 / 74 | |
| 12.48.0 | 35 / 74 | |
| 12.47.1 | 35 / 74 | |
| 12.47.0 | 35 / 74 | |
| 12.46.1 | 35 / 74 | |
| 12.46.0 | 35 / 74 | |
| 12.45.0 | 35 / 74 | |
| 12.44.0 | 35 / 74 | |
| 12.43.0 | 35 / 74 | |
| 12.42.0 | 35 / 74 | |
| 12.41.0 | 35 / 74 | |
| 12.40.0 | 35 / 74 | |
| 12.39.0 | 35 / 74 | |
| 12.38.0 | 36 / 72 | |
| 12.37.0 | 36 / 72 | |
| 12.36.0 | 36 / 72 | |
| 12.35.0 | 36 / 72 | |
| 12.34.1 | 36 / 72 | |
| 12.34.0 | 36 / 72 | |
| 12.33.0 | 36 / 75 | |
| 12.32.0 | 36 / 75 | |
| 12.31.0 | 36 / 75 |
v12.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.