@ionic/discover
Simple UDP based protocol for service discovery implemented in pure JS.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from individual Ionic dev (dwieeb) to official ionicjs org account in 2020 — a legitimate organizational consolidation. ionicjs has 701 approved packages and 0 rejected. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer dallasjames is part of the Ionic team; addition is consistent with normal team management within the official Ionic org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of camwiegert reflects normal team turnover within the Ionic organization; no takeover indicators present. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; commonly used as an implicit dependency in TypeScript-compiled packages. Not a security concern. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 3.1.8 | 4 / 11 | |
| 3.1.7 | 4 / 11 | |
| 3.1.6 | 4 / 11 | |
| 3.1.5 | 4 / 11 | |
| 3.1.4 | 4 / 12 | |
| 3.1.3 | 4 / 12 | |
| 3.1.2 | 4 / 12 | |
| 3.1.1 | 4 / 12 | |
| 3.1.0 | 4 / 12 | |
| 3.0.2 | 4 / 12 | |
| 3.0.1 | 4 / 12 | |
| 3.0.0 | 4 / 12 | |
| 2.0.8 | 4 / 12 | |
| 2.0.7 | 4 / 12 | |
| 2.0.6 | 4 / 12 | |
| 2.0.5 | 4 / 12 | |
| 2.0.4 | 4 / 12 | |
| 2.0.3 | 4 / 12 | |
| 2.0.2 | 4 / 12 | |
| 2.0.1 | 4 / 12 | |
| 2.0.0 | 4 / 12 | |
| 1.0.13 | 4 / 12 | |
| 1.0.12 | 4 / 12 | |
| 1.0.11 | 4 / 12 | |
| 1.0.10 | 4 / 12 | |
| 1.0.9 | 4 / 12 | |
| 1.0.8 | 4 / 12 | |
| 1.0.7 | 4 / 12 | |
| 1.0.6 | 4 / 11 | |
| 1.0.5 | 4 / 11 | |
| 1.0.4 | 4 / 11 | |
| 1.0.3 | 4 / 11 | |
| 1.0.2 | 4 / 11 | |
| 1.0.1 | 4 / 11 | |
| 1.0.0 | 4 / 10 | |
| 0.4.0 | 1 / 12 | |
| 0.3.3 | 1 / 12 | |
| 0.3.2 | 1 / 12 | |
| 0.3.1 | 1 / 12 | |
| 0.3.0 | 1 / 12 | |
| 0.2.1 | 1 / 11 | |
| 0.2.0 | 1 / 11 | |
| 0.1.0 | 1 / 11 | |
| 0.0.10 | 1 / 10 | |
| 0.0.9 | 1 / 10 | |
| 0.0.8 | 1 / 10 | |
| 0.0.6 | 1 / 10 | |
| 0.0.5 | 1 / 10 | |
| 0.0.4 | 1 / 7 | |
| 0.0.3 | 1 / 7 | |
| 0.0.2 | 1 / 7 |
v3.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
2 findingsThis version was published by a different npm account than previous versions on 2020-08-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
2 findingsThis version was published by a different npm account than previous versions on 2020-08-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-06. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-03. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.