@applitools/monitoring-commons
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:@applitools/monitoring-commons | AI (phantom-deps): Self-referential version pin within same org scope, not a real phantom import risk. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): debug is declared in dependencies; heuristic false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.1.4 | 0 / 12 | |
| 2.1.3 | 1 / 12 | |
| 2.1.2 | 1 / 12 | |
| 2.1.1 | 1 / 12 | |
| 2.1.0 | 1 / 12 | |
| 1.0.19 | 1 / 8 |
v2.1.0
2 findingsThis version was published by a different npm account (ronikar_applitools) than the most recent previously approved version (amirhalatzi) on 2025-02-24. It has since remained available on npm for 509 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.