@soltracer/nft-staking
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Minimal metadata is a stable trait of this internal @soltracer library, not spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Missing description is consistent across this package's releases; benign. | ai | |
| phantom-deps | phantom-dep:@soltracer/cpi-accounts | AI (phantom-deps): Same-org internal dependency, plausibly used indirectly via build output. | ai | |
| provenance | missing-githead | AI (provenance): Small publisher's CI setup varies release to release; no behavior change observed. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 5 / 2 | |
| 0.7.48 | 5 / 2 | |
| 0.7.47 | 5 / 2 | |
| 0.7.46 | 5 / 2 | |
| 0.7.45 | 5 / 2 | |
| 0.7.44 | 5 / 2 | |
| 0.7.43 | 5 / 2 | |
| 0.7.42 | 5 / 2 | |
| 0.7.41 | 5 / 2 | |
| 0.7.40 | 5 / 2 | |
| 0.7.39 | 5 / 2 | |
| 0.7.38 | 5 / 2 | |
| 0.7.37 | 4 / 2 | |
| 0.7.36 | 4 / 2 | |
| 0.7.35 | 4 / 2 | |
| 0.7.34 | 4 / 2 | |
| 0.7.33 | 3 / 1 | |
| 0.7.32 | 3 / 1 | |
| 0.7.31 | 3 / 1 | |
| 0.7.30 | 3 / 1 | |
| 0.7.29 | 3 / 1 | |
| 0.7.28 | 3 / 1 | |
| 0.7.27 | 3 / 1 | |
| 0.7.26 | 3 / 1 | |
| 0.7.25 | 3 / 1 | |
| 0.7.24 | 3 / 1 | |
| 0.7.23 | 3 / 1 | |
| 0.7.22 | 3 / 1 | |
| 0.7.21 | 3 / 1 | |
| 0.7.19 | 3 / 1 | |
| 0.7.18 | 3 / 1 | |
| 0.7.16 | 3 / 1 | |
| 0.7.15 | 3 / 1 | |
| 0.7.14 | 3 / 1 | |
| 0.7.10 | 3 / 1 | |
| 0.7.9 | 3 / 1 | |
| 0.7.8 | 3 / 1 | |
| 0.7.7 | 3 / 1 | |
| 0.7.6 | 3 / 1 | |
| 0.7.5 | 3 / 1 | |
| 0.7.4 | 3 / 1 | |
| 0.7.3 | 3 / 1 | |
| 0.7.2 | 3 / 1 | |
| 0.7.1 | 3 / 1 | |
| 0.7.0 | 3 / 1 | |
| 0.6.6 | 3 / 1 | |
| 0.6.5 | 3 / 1 | |
| 0.6.4 | 3 / 1 | |
| 0.6.3 | 3 / 1 | |
| 0.6.2 | 3 / 1 | |
| 0.6.1 | 3 / 1 | |
| 0.6.0 | 3 / 1 | |
| 0.5.1 | 3 / 1 | |
| 0.5.0 | 3 / 1 | |
| 0.4.0 | 3 / 1 | |
| 0.3.1 | 3 / 1 | |
| 0.3.0 | 3 / 1 | |
| 0.2.9 | 3 / 1 | |
| 0.2.8 | 3 / 1 | |
| 0.2.7 | 3 / 1 | |
| 0.2.6 | 3 / 1 | |
| 0.2.5 | 3 / 1 | |
| 0.2.4 | 3 / 1 | |
| 0.2.3 | 3 / 1 | |
| 0.2.1 | 1 / 1 | |
| 0.2.0 | 1 / 1 | |
| 0.1.0 | 1 / 1 |
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.36
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: syndicure.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.35
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: syndicure.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.34
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: syndicure.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.