@almadar/operators
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with clean track record and no other risk signals; lack of Sigstore provenance is a hygiene concern, not a security threat for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 5 | |
| 2.3.0 | 0 / 5 | |
| 2.2.0 | 0 / 5 | |
| 2.1.3 | 0 / 5 | |
| 2.1.2 | 0 / 5 | |
| 2.1.1 | 0 / 5 | |
| 2.1.0 | 0 / 5 | |
| 2.0.7 | 0 / 5 | |
| 2.0.6 | 0 / 5 | |
| 2.0.5 | 0 / 5 | |
| 2.0.4 | 0 / 5 | |
| 2.0.3 | 0 / 5 | |
| 2.0.2 | 0 / 2 | |
| 2.0.1 | 0 / 2 | |
| 2.0.0 | 0 / 2 | |
| 1.0.14 | 0 / 2 | |
| 1.0.13 | 0 / 2 | |
| 1.0.12 | 0 / 2 | |
| 1.0.11 | 0 / 2 | |
| 1.0.10 | 0 / 2 | |
| 1.0.9 | 0 / 2 | |
| 0.1.0 | 0 / 2 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.