@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 | AI (phantom-deps): jest is a test framework referenced in config/scripts, not imported at runtime; stable false positive. | 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 | |
| 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 | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a proxy handler for monitoring middleware — standard JS proxy pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:endent | AI (phantom-deps): endent is listed as a runtime dependency; phantom-dep heuristic false positive. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
2 findingsSpreading entire process.env into an object — may capture all secrets 102 | 103 | case '/env': { > 104 | res.json({ 105 | ...process.env, 106 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.66.0
2 findingsSpreading entire process.env into an object — may capture all secrets 102 | 103 | case '/env': { > 104 | res.json({ 105 | ...process.env, 106 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.0
2 findingsSpreading entire process.env into an object — may capture all secrets 102 | 103 | case '/env': { > 104 | res.json({ 105 | ...process.env, 106 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.0
2 findingsSpreading entire process.env into an object — may capture all secrets 102 | 103 | case '/env': { > 104 | res.json({ 105 | ...process.env, 106 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.0
2 findingsSpreading entire process.env into an object — may capture all secrets 102 | 103 | case '/env': { > 104 | res.json({ 105 | ...process.env, 106 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
2 findingsSpreading entire process.env into an object — may capture all secrets 102 | 103 | case '/env': { > 104 | res.json({ 105 | ...process.env, 106 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.0
2 findingsSpreading entire process.env into an object — may capture all secrets 100 | 101 | case '/env': { > 102 | res.json({ 103 | ...process.env, 104 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.0
2 findingsSpreading entire process.env into an object — may capture all secrets 100 | 101 | case '/env': { > 102 | res.json({ 103 | ...process.env, 104 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.5
2 findingsSpreading entire process.env into an object — may capture all secrets 100 | 101 | case '/env': { > 102 | res.json({ 103 | ...process.env, 104 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.4
2 findingsSpreading entire process.env into an object — may capture all secrets 100 | 101 | case '/env': { > 102 | res.json({ 103 | ...process.env, 104 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.