@operato/app
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @operato/app cannot typosquat bare package hapi; edit-distance match is spurious. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @operato/app cannot typosquat bare package pg; edit-distance match is spurious. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @operato/app cannot typosquat bare package yup; edit-distance match is spurious. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @operato/app cannot typosquat bare package ajv; edit-distance match is spurious. | ai | |
| phantom-deps | phantom-dep:@operato/shell | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@operato/property-panel | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:codemirror | AI (phantom-deps): codemirror is a declared dep used via config files; phantom-dep heuristic fires on config-only references. | ai | |
| phantom-deps | phantom-dep:graphql-config | AI (phantom-deps): graphql-config declared dep used in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@codemirror/state | AI (phantom-deps): Declared dep referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/delegate | AI (phantom-deps): Declared dep; phantom-dep heuristic fires on config-only references, stable false positive. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 9.2.25 | 29 / 17 | |
| 9.2.23 | 29 / 17 | |
| 9.2.22 | 29 / 17 | |
| 9.2.21 | 29 / 17 | |
| 9.2.20 | 29 / 17 | |
| 9.2.19 | 29 / 17 | |
| 9.2.14 | 29 / 17 | |
| 9.2.13 | 29 / 17 | |
| 9.2.6 | 29 / 17 | |
| 9.2.5 | 29 / 17 | |
| 9.2.1 | 29 / 17 | |
| 9.2.0 | 29 / 17 | |
| 8.2.20 | 28 / 17 | |
| 8.2.19 | 28 / 17 | |
| 8.2.18 | 28 / 17 | |
| 8.2.17 | 28 / 17 | |
| 8.2.16 | 28 / 17 | |
| 8.2.15 | 28 / 17 | |
| 8.2.14 | 28 / 17 | |
| 8.2.13 | 28 / 17 |
v9.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.