@xapp/contact-capture-handler
A data driven contact information collector for 📣 stentor
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): Transition to GitHub Actions publisher with SLSA attestation is expected CI/CD automation for this org. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 0 / 36 | |
| 2.0.0 | 0 / 36 | |
| 1.22.4 | 0 / 36 | |
| 1.22.3 | 0 / 36 | |
| 1.22.2 | 0 / 36 | |
| 1.22.1 | 0 / 36 | |
| 1.22.0 | 0 / 36 | |
| 1.21.1 | 0 / 36 | |
| 1.21.0 | 0 / 36 | |
| 1.20.0 | 0 / 36 | |
| 1.19.1 | 0 / 36 | |
| 1.19.0 | 0 / 36 | |
| 1.18.0 | 0 / 36 | |
| 1.17.1 | 0 / 36 | |
| 1.17.0 | 0 / 36 | |
| 1.16.1 | 0 / 36 | |
| 1.15.7 | 0 / 36 | |
| 1.15.6 | 0 / 36 | |
| 1.15.5 | 0 / 36 | |
| 1.15.4 | 0 / 36 | |
| 1.15.3 | 0 / 36 | |
| 1.15.2 | 0 / 36 | |
| 1.15.1 | 0 / 36 | |
| 1.15.0 | 0 / 36 | |
| 1.14.1 | 0 / 36 | |
| 1.14.0 | 0 / 36 | |
| 1.13.5 | 0 / 36 | |
| 1.13.4 | 0 / 36 | |
| 1.13.3 | 0 / 36 | |
| 1.13.2 | 0 / 36 | |
| 1.13.1 | 0 / 36 | |
| 1.13.0 | 0 / 36 | |
| 1.12.3 | 0 / 36 | |
| 1.12.2 | 0 / 36 | |
| 1.12.1 | 0 / 36 | |
| 1.12.0 | 0 / 36 | |
| 1.11.15 | 0 / 36 | |
| 1.11.14 | 0 / 36 | |
| 1.11.13 | 0 / 36 | |
| 1.11.12 | 0 / 36 | |
| 1.11.11 | 0 / 36 | |
| 1.11.10 | 0 / 36 | |
| 1.11.9 | 0 / 36 | |
| 1.11.8 | 0 / 30 | |
| 1.11.7 | 0 / 30 | |
| 1.11.6 | 0 / 30 | |
| 1.11.5 | 0 / 30 | |
| 1.11.4 | 0 / 30 | |
| 1.11.3 | 0 / 30 | |
| 1.11.2 | 0 / 30 | |
| 1.11.1 | 0 / 30 | |
| 1.11.0 | 0 / 30 |
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.