@nsshunt/stsmessaging
STS Messeging
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): tiny-emitter is a small, well-known established dependency. | ai | |
| provenance | missing-githead | AI (provenance): Metadata regression only, no behavioral signal; publisher has long clean history. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README is stylistic, not spam; established internal-style package. | ai |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 1.0.75 | 4 / 10 | |
| 1.0.74 | 4 / 10 | |
| 1.0.73 | 4 / 10 | |
| 1.0.72 | 4 / 10 | |
| 1.0.71 | 4 / 10 | |
| 1.0.70 | 4 / 10 | |
| 1.0.69 | 4 / 10 | |
| 1.0.68 | 4 / 10 | |
| 1.0.67 | 4 / 10 | |
| 1.0.66 | 4 / 10 | |
| 1.0.65 | 4 / 10 | |
| 1.0.64 | 4 / 10 | |
| 1.0.63 | 4 / 10 | |
| 1.0.62 | 4 / 10 | |
| 1.0.61 | 4 / 10 | |
| 1.0.59 | 4 / 9 | |
| 1.0.58 | 4 / 9 | |
| 1.0.57 | 4 / 9 | |
| 1.0.56 | 5 / 9 | |
| 1.0.55 | 5 / 9 | |
| 1.0.54 | 5 / 9 | |
| 1.0.53 | 5 / 9 | |
| 1.0.52 | 5 / 9 | |
| 1.0.51 | 5 / 9 | |
| 1.0.50 | 5 / 9 | |
| 1.0.49 | 5 / 9 | |
| 1.0.48 | 5 / 9 | |
| 1.0.47 | 5 / 9 | |
| 1.0.46 | 5 / 9 | |
| 1.0.45 | 5 / 9 | |
| 1.0.44 | 5 / 9 | |
| 1.0.43 | 5 / 9 | |
| 1.0.42 | 5 / 9 | |
| 1.0.41 | 5 / 9 | |
| 1.0.40 | 5 / 9 | |
| 1.0.39 | 5 / 9 | |
| 1.0.38 | 5 / 10 | |
| 1.0.37 | 5 / 10 | |
| 1.0.36 | 5 / 10 | |
| 1.0.35 | 5 / 10 | |
| 1.0.34 | 5 / 10 | |
| 1.0.33 | 5 / 10 | |
| 1.0.32 | 5 / 10 | |
| 1.0.31 | 5 / 10 | |
| 1.0.30 | 5 / 10 | |
| 1.0.29 | 5 / 10 | |
| 1.0.28 | 5 / 10 | |
| 1.0.27 | 5 / 10 | |
| 1.0.26 | 5 / 10 | |
| 1.0.25 | 5 / 10 | |
| 1.0.24 | 5 / 10 |
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
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: nsshunt.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
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: nsshunt.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
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: nsshunt.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
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: nsshunt.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
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: nsshunt.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
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: nsshunt.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.