@barchart/common-node-js
Common classes, utilities, and functions for building Node.js servers
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:xml2js | AI (phantom-deps): Config-referenced, not import. | ai | |
| phantom-deps | phantom-dep:http-digest-client | AI (phantom-deps): Config-referenced, not import. | ai | |
| phantom-deps | phantom-dep:@barchart/marketdata-api-js | AI (phantom-deps): Same-org scope dependency, benign. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): Config-referenced, not import; longstanding pattern for this package. | ai | |
| phantom-deps | phantom-dep:numeral | AI (phantom-deps): Config-referenced, not import. | ai | |
| phantom-deps | phantom-dep:moment-timezone | AI (phantom-deps): moment-timezone is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used in DynamoDB BinarySerializer for legitimate deserialization of stored binary attributes. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 5.2.1 | 27 / 3 | |
| 5.2.0 | 27 / 3 | |
| 5.1.1 | 27 / 3 | |
| 5.1.0 | 27 / 3 | |
| 5.0.0 | 30 / 3 | |
| 4.74.1 | 20 / 7 | |
| 4.74.0 | 20 / 7 | |
| 4.73.0 | 20 / 7 | |
| 4.72.2 | 20 / 7 | |
| 4.72.1 | 20 / 7 | |
| 4.72.0 | 20 / 7 | |
| 4.71.0 | 20 / 7 | |
| 4.70.0 | 20 / 7 | |
| 4.68.0 | 20 / 7 | |
| 4.67.2 | 20 / 7 | |
| 4.67.1 | 20 / 7 | |
| 4.67.0 | 20 / 7 | |
| 4.66.1 | 20 / 7 | |
| 4.65.2 | 20 / 7 | |
| 4.65.1 | 20 / 7 | |
| 4.65.0 | 20 / 7 | |
| 4.64.0 | 20 / 7 | |
| 4.63.0 | 20 / 7 | |
| 4.62.0 | 20 / 7 | |
| 4.60.0 | 20 / 7 | |
| 4.59.1 | 20 / 7 | |
| 4.59.0 | 20 / 7 | |
| 4.58.0 | 20 / 7 | |
| 4.57.0 | 20 / 7 | |
| 4.56.0 | 20 / 7 | |
| 4.55.1 | 20 / 7 | |
| 4.55.0 | 20 / 7 | |
| 4.54.3 | 20 / 7 | |
| 4.54.2 | 20 / 7 | |
| 4.54.1 | 20 / 7 | |
| 4.54.0 | 20 / 7 | |
| 4.53.5 | 20 / 7 | |
| 4.53.4 | 20 / 7 | |
| 4.53.3 | 20 / 7 | |
| 4.53.2 | 20 / 7 | |
| 4.53.1 | 20 / 7 | |
| 4.53.0 | 20 / 7 | |
| 4.52.0 | 20 / 7 | |
| 4.51.0 | 20 / 7 | |
| 4.50.1 | 20 / 7 | |
| 4.50.0 | 20 / 7 | |
| 4.49.3 | 20 / 7 | |
| 4.49.2 | 20 / 7 | |
| 4.49.1 | 20 / 7 | |
| 4.49.0 | 20 / 7 | |
| 4.48.1 | 20 / 7 | |
| 4.48.0 | 20 / 7 | |
| 4.47.0 | 20 / 7 | |
| 4.46.1 | 20 / 7 | |
| 4.45.0 | 20 / 7 | |
| 4.44.1 | 20 / 7 | |
| 4.44.0 | 20 / 7 | |
| 4.43.0 | 20 / 7 | |
| 4.42.1 | 20 / 7 | |
| 4.42.0 | 20 / 7 | |
| 4.41.0 | 20 / 7 | |
| 4.40.0 | 20 / 7 |
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (luka.sotra) than the most recent previously approved version (bryan.ingle) on 2026-07-14, but luka.sotra is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.54.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bryan.ingle) than the most recent previously approved version (luka.sotra) on 2025-04-28, but bryan.ingle is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.54.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.54.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.54.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bryan.ingle) than the most recent previously approved version (luka.sotra) on 2025-04-03, but bryan.ingle is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.53.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.53.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.53.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (luka.sotra) than the most recent previously approved version (bryan.ingle) on 2025-03-21, but luka.sotra is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.53.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.49.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.49.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.