@artel/en-reactivity
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:reactronic | AI (phantom-deps): reactronic is the sole dependency and likely re-exported via config/barrel; phantom-dep false positive for this thin wrapper package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.96.26028 | 1 / 0 | |
| 0.96.26027 | 1 / 0 | |
| 0.96.26026 | 1 / 0 | |
| 0.96.26025 | 1 / 0 | |
| 0.96.26024 | 1 / 0 | |
| 0.96.26015 | 1 / 0 | |
| 0.96.26014 | 1 / 0 | |
| 0.96.26013 | 1 / 0 | |
| 0.96.26012 | 1 / 0 | |
| 0.96.26011 | 1 / 0 | |
| 0.96.26010 | 1 / 0 | |
| 0.95.25048 | 1 / 0 | |
| 0.95.25045 | 1 / 0 | |
| 0.94.25045 | 1 / 0 | |
| 0.94.25031 | 1 / 0 | |
| 0.94.25030 | 1 / 0 | |
| 0.94.25029 | 1 / 0 | |
| 0.93.25026 | 1 / 0 | |
| 0.93.25025 | 1 / 0 | |
| 0.92.25013 | 1 / 0 | |
| 0.92.25012 | 1 / 0 | |
| 0.92.25011 | 1 / 0 | |
| 0.92.25009 | 1 / 0 | |
| 0.92.25008 | 1 / 0 | |
| 0.92.25006 | 1 / 0 | |
| 0.9.26019 | 1 / 0 | |
| 0.9.26016 | 1 / 0 | |
| 0.9.26008 | 1 / 0 | |
| 0.9.26003 | 1 / 0 |
v0.93.25025
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.25013
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.25012
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.25011
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.25009
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.25008
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.25006
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.26019
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.