@donmahallem/rxjs-zone
Helper for handling zone.js with rxjs
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.6.66 | 0 / 2 | |
| 0.6.65 | 0 / 2 | |
| 0.6.64 | 0 / 2 | |
| 0.6.63 | 0 / 2 | |
| 0.6.62 | 0 / 2 | |
| 0.6.61 | 0 / 2 | |
| 0.6.60 | 0 / 2 | |
| 0.6.59 | 0 / 2 | |
| 0.6.58 | 0 / 2 | |
| 0.6.57 | 0 / 2 | |
| 0.6.56 | 0 / 2 | |
| 0.6.55 | 0 / 2 | |
| 0.6.54 | 0 / 2 | |
| 0.6.53 | 0 / 2 | |
| 0.6.52 | 0 / 2 | |
| 0.6.51 | 0 / 2 | |
| 0.6.50 | 0 / 2 | |
| 0.6.49 | 0 / 2 | |
| 0.6.48 | 0 / 2 | |
| 0.6.47 | 0 / 2 | |
| 0.6.46 | 0 / 2 | |
| 0.6.45 | 0 / 2 | |
| 0.6.44 | 0 / 2 | |
| 0.6.43 | 0 / 2 | |
| 0.6.42 | 0 / 2 | |
| 0.6.41 | 0 / 2 | |
| 0.6.40 | 0 / 2 | |
| 0.6.39 | 0 / 2 | |
| 0.6.38 | 0 / 2 | |
| 0.6.37 | 0 / 2 | |
| 0.6.36 | 0 / 2 | |
| 0.6.35 | 0 / 2 | |
| 0.6.6 | 0 / 2 | |
| 0.6.5 | 0 / 2 | |
| 0.6.4 | 0 / 2 | |
| 0.6.3 | 0 / 2 | |
| 0.6.2 | 0 / 2 | |
| 0.6.1 | 0 / 2 | |
| 0.6.0 | 0 / 2 |
v0.6.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.