@axinom/mosaic-service-common
Common helpers and PostgreSQL-related functionality
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:src/common/logging/logger.spec.ts | AI (source-diff): Random string test fixture in spec file, not an encoded payload. | ai | |
| source-diff | encoded-string-file:src/common/signing/generate-signature.spec.ts | AI (source-diff): Test fixture RSA private key used to unit-test signature generation, not a payload. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Types package, loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Types package, loaded by convention. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Intentional /env debug endpoint in a service-common library; design choice, not malicious. | ai | |
| phantom-deps | phantom-dep:jest-expect-message | AI (phantom-deps): Test utility referenced in jest config only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:jest | AI (phantom-deps): jest is a test framework referenced in config/scripts, not imported at runtime; stable false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Used for JWT payload decoding in a logging/masking middleware — standard and benign pattern. | ai | |
| phantom-deps | phantom-dep:@types/verror | AI (phantom-deps): Type package for verror which is a runtime dep; framework-scoped, stable false positive. | ai | |
| phantom-deps | phantom-dep:endent | AI (phantom-deps): endent is listed as a runtime dependency; phantom-dep heuristic false positive. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a proxy handler for monitoring middleware — standard JS proxy pattern, not obfuscation. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.70.0 | 20 / 11 | |
| 0.69.0 | 19 / 13 | |
| 0.68.0 | 19 / 13 | |
| 0.67.0 | 19 / 13 | |
| 0.66.0 | 21 / 12 | |
| 0.65.0 | 21 / 12 | |
| 0.64.0 | 21 / 12 | |
| 0.63.0 | 21 / 12 | |
| 0.62.0 | 20 / 13 | |
| 0.61.0 | 20 / 13 | |
| 0.60.0 | 20 / 13 | |
| 0.59.5 | 20 / 13 | |
| 0.59.4 | 20 / 13 | |
| 0.59.3 | 20 / 13 | |
| 0.59.2 | 20 / 13 | |
| 0.59.1 | 20 / 13 | |
| 0.59.0 | 20 / 13 | |
| 0.58.0 | 20 / 13 | |
| 0.57.0 | 20 / 13 | |
| 0.56.0 | 20 / 12 | |
| 0.55.0 | 20 / 12 | |
| 0.54.0 | 20 / 12 | |
| 0.53.0 | 20 / 12 | |
| 0.52.0 | 20 / 12 | |
| 0.51.0 | 20 / 12 | |
| 0.50.0 | 20 / 12 | |
| 0.49.0 | 20 / 12 | |
| 0.48.1 | 20 / 12 |
v0.70.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.3
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.2
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.1
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.