@sebspark/pubsub
A wrapper around [@google-cloud/pubsub](https://www.npmjs.com/package/@google-cloud/pubsub) adding simple methods for publishing and subscribing with typed messages.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/html-escaper | AI (dependencies): @types/html-escaper is a type-definition-only package with no runtime code; negligible risk. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a runtime dep used for HTTP push subscription handling; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:html-escaper | AI (phantom-deps): html-escaper is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type-only dep for express; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/html-escaper | AI (phantom-deps): Type-only dep; stable false positive for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.8.3 | 6 / 2 | |
| 1.8.2 | 6 / 2 | |
| 1.8.1 | 6 / 2 | |
| 1.8.0 | 6 / 2 | |
| 1.7.2 | 6 / 2 | |
| 1.7.1 | 6 / 2 | |
| 1.7.0 | 6 / 2 | |
| 1.6.2 | 6 / 1 | |
| 1.6.1 | 6 / 1 | |
| 1.6.0 | 6 / 1 | |
| 1.5.6 | 6 / 1 | |
| 1.5.5 | 6 / 1 | |
| 1.5.4 | 6 / 1 | |
| 1.5.3 | 6 / 1 | |
| 1.5.2 | 6 / 1 | |
| 1.5.1 | 6 / 1 | |
| 1.5.0 | 6 / 1 | |
| 1.4.0 | 6 / 1 | |
| 1.3.1 | 6 / 1 | |
| 1.3.0 | 6 / 1 | |
| 1.2.0 | 6 / 1 | |
| 1.1.2 | 6 / 1 | |
| 1.1.1 | 6 / 1 | |
| 1.1.0 | 6 / 1 | |
| 1.0.0 | 8 / 1 |
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.