@astrojs/rss
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped official Astro package; not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Scoped official Astro package; not a typosquat of rxjs. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.0.19 | 3 / 3 | |
| 4.0.18 | 3 / 3 | |
| 4.0.17 | 3 / 3 | |
| 4.0.16 | 3 / 3 | |
| 4.0.15 | 2 / 4 | |
| 4.0.14 | 2 / 4 | |
| 4.0.13 | 2 / 4 | |
| 4.0.12 | 2 / 4 | |
| 4.0.11 | 2 / 4 | |
| 4.0.10 | 2 / 4 | |
| 4.0.9 | 2 / 4 | |
| 4.0.8 | 2 / 4 | |
| 4.0.7 | 2 / 4 | |
| 4.0.6 | 2 / 4 |
v4.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.