@sebspark/logging
A pubsub subscriber helper.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): CI/CD publishing with SLSA provenance; removal consistent with org-level automation replacing individual maintainers. | ai | |
| dependencies | unvetted-dep:socketio-wildcard | AI (dependencies): socketio-wildcard is a small, pinned utility used alongside socket.io in this logging package; no known advisories and stable usage pattern. | ai | |
| phantom-deps | phantom-dep:winston-transport | AI (phantom-deps): winston-transport used for type extension; stable false positive for this logging package. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Logging middleware that wraps express; declared as peer/runtime dep, not directly imported at top level. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate internal monorepo package from seb-oss/Spark-packages; sparse README is expected for internal tooling. | ai | |
| phantom-deps | phantom-dep:@types/express-serve-static-core | AI (phantom-deps): Type-only dependency loaded by convention for express type augmentation; stable false positive. | ai | |
| phantom-deps | phantom-dep:logform | AI (phantom-deps): logform is a winston sub-dependency used for type augmentation; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.0.13 | 8 / 3 | |
| 2.0.12 | 8 / 3 | |
| 2.0.11 | 8 / 3 | |
| 2.0.10 | 8 / 3 | |
| 2.0.9 | 8 / 3 | |
| 2.0.8 | 8 / 3 | |
| 2.0.7 | 8 / 4 | |
| 2.0.6 | 8 / 4 | |
| 2.0.5 | 8 / 4 | |
| 2.0.4 | 8 / 4 | |
| 2.0.3 | 8 / 4 | |
| 2.0.2 | 8 / 4 | |
| 2.0.1 | 8 / 4 | |
| 2.0.0 | 8 / 4 |
v2.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.