@logto/connector-apple
Apple web connector implementation.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher change is a known maintainer; no code changes from prior approved version. | ai | |
| provenance | no-provenance | AI (provenance): Established Logto ecosystem package; absence of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:got | AI (phantom-deps): got is a declared runtime dependency; phantom-dep is a false positive for this package's import style. | ai | |
| phantom-deps | phantom-dep:snakecase-keys | AI (phantom-deps): snakecase-keys is a declared runtime dependency; phantom-dep is a false positive for this package's import style. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.6.6 | 7 / 13 | |
| 1.6.5 | 7 / 13 | |
| 1.6.4 | 7 / 13 | |
| 1.6.3 | 7 / 13 | |
| 1.6.2 | 7 / 13 | |
| 1.6.0 | 7 / 13 |
v1.6.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (simeng_li) than the most recent previously approved version (gaosun) on 2026-05-29, but simeng_li is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.