@stackone/expressions
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:jexl | AI (phantom-deps): Runtime dependency used indirectly; declared and present in dependencies. | ai | |
| phantom-deps | phantom-dep:jsonpath-plus | AI (phantom-deps): Runtime dependency used indirectly; declared and present in dependencies. | ai | |
| phantom-deps | phantom-dep:@stackone/utils | AI (phantom-deps): Same-org scoped dependency; declared and present in dependencies. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.34.1 | 3 / 2 | |
| 0.34.0 | 3 / 2 | |
| 0.33.0 | 3 / 2 | |
| 0.32.0 | 3 / 2 | |
| 0.31.2 | 3 / 2 | |
| 0.31.0 | 3 / 2 | |
| 0.30.0 | 3 / 2 | |
| 0.29.0 | 3 / 2 | |
| 0.28.0 | 3 / 2 | |
| 0.27.0 | 3 / 2 | |
| 0.26.0 | 3 / 2 | |
| 0.25.1 | 3 / 2 | |
| 0.25.0 | 3 / 2 | |
| 0.24.0 | 3 / 2 | |
| 0.23.0 | 3 / 2 | |
| 0.22.0 | 3 / 2 | |
| 0.21.0 | 3 / 2 | |
| 0.20.0 | 3 / 2 | |
| 0.19.1 | 3 / 2 | |
| 0.19.0 | 3 / 2 | |
| 0.18.1 | 3 / 2 | |
| 0.18.0 | 3 / 2 | |
| 0.17.0 | 3 / 2 | |
| 0.16.0 | 3 / 2 | |
| 0.15.3 | 4 / 2 | |
| 0.15.2 | 4 / 2 | |
| 0.15.1 | 4 / 2 | |
| 0.14.0 | 4 / 2 | |
| 0.13.0 | 4 / 3 | |
| 0.12.0 | 4 / 3 | |
| 0.11.0 | 4 / 3 | |
| 0.10.2 | 4 / 3 | |
| 0.9.0 | 4 / 3 | |
| 0.8.0 | 4 / 3 | |
| 0.7.0 | 4 / 3 | |
| 0.6.1 | 4 / 3 | |
| 0.6.0 | 4 / 3 | |
| 0.5.0 | 4 / 3 | |
| 0.4.1 | 4 / 3 | |
| 0.4.0 | 4 / 3 | |
| 0.3.1 | 3 / 2 | |
| 0.3.0 | 3 / 2 | |
| 0.2.0 | 2 / 1 | |
| 0.1.0 | 2 / 1 |
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.