@operato/property-panel
Webcomponent property-panel following open-wc recommendations
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@operato/utils | AI (phantom-deps): Same-org sibling dep; declared in package.json and likely used transitively or indirectly within the monorepo. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 9.2.25 | 7 / 18 | |
| 9.2.23 | 7 / 18 | |
| 9.2.22 | 7 / 18 | |
| 9.2.21 | 7 / 18 | |
| 9.2.20 | 7 / 18 | |
| 9.2.19 | 7 / 18 | |
| 9.2.12 | 7 / 18 | |
| 9.2.7 | 7 / 18 | |
| 9.2.6 | 7 / 18 | |
| 9.2.5 | 7 / 18 | |
| 9.2.1 | 7 / 18 | |
| 9.2.0 | 7 / 18 |
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.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.7
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.