bonjour-hap
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.10.4 | 3 / 5 | |
| 3.10.3 | 3 / 5 | |
| 3.10.2 | 3 / 5 | |
| 3.10.1 | 3 / 5 | |
| 3.10.0 | 3 / 5 | |
| 3.9.1 | 4 / 5 | |
| 3.9.0 | 4 / 5 | |
| 3.8.0 | 4 / 5 | |
| 3.7.3 | 4 / 5 | |
| 3.7.2 | 4 / 5 | |
| 3.7.1 | 4 / 5 | |
| 3.7.0 | 4 / 5 | |
| 3.6.5 | 4 / 5 | |
| 3.6.4 | 5 / 5 | |
| 3.6.3 | 5 / 5 | |
| 3.6.2 | 5 / 5 | |
| 3.6.1 | 5 / 5 | |
| 3.6.0 | 5 / 5 | |
| 3.5.11 | 5 / 5 | |
| 3.5.10 | 5 / 5 | |
| 3.5.9 | 5 / 5 | |
| 3.5.8 | 5 / 5 | |
| 3.5.7 | 5 / 5 | |
| 3.5.6 | 4 / 5 | |
| 3.5.5 | 4 / 3 | |
| 3.5.4 | 6 / 4 | |
| 3.5.1 | 6 / 4 | |
| 3.5.0 | 6 / 4 |
v3.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (supereg) than the most recent previously approved version (khaost) on 2020-12-16, but supereg 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.
v3.6.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (khaost) than the most recent previously approved version (supereg) on 2020-12-16, but khaost 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.
v3.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (supereg) than the most recent previously approved version (khaost) on 2020-12-16, but supereg 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.
v3.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.