@barchart/common-js
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): luka.sotra is a listed contributor with barchart.com email; legitimate org-internal handoff. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 5.2.1 | 3 / 5 | |
| 5.2.0 | 3 / 5 | |
| 5.1.1 | 3 / 5 | |
| 5.1.0 | 3 / 5 | |
| 5.0.0 | 3 / 5 | |
| 4.74.1 | 6 / 13 | |
| 4.74.0 | 6 / 13 | |
| 4.73.0 | 6 / 13 | |
| 4.72.2 | 6 / 13 | |
| 4.72.1 | 6 / 13 | |
| 4.72.0 | 6 / 13 | |
| 4.71.0 | 6 / 13 | |
| 4.70.0 | 6 / 13 | |
| 4.68.0 | 6 / 13 | |
| 4.67.2 | 6 / 13 | |
| 4.67.1 | 6 / 13 | |
| 4.67.0 | 6 / 13 | |
| 4.66.1 | 6 / 13 | |
| 4.66.0 | 6 / 13 | |
| 4.65.2 | 6 / 13 | |
| 4.65.1 | 6 / 13 | |
| 4.65.0 | 6 / 13 | |
| 4.64.0 | 6 / 13 | |
| 4.63.0 | 6 / 13 | |
| 4.62.0 | 6 / 13 | |
| 4.61.0 | 6 / 13 | |
| 4.60.0 | 6 / 13 | |
| 4.59.1 | 6 / 13 | |
| 4.59.0 | 6 / 13 | |
| 4.58.0 | 6 / 13 | |
| 4.57.0 | 6 / 13 | |
| 4.56.0 | 6 / 13 | |
| 4.55.1 | 6 / 13 | |
| 4.55.0 | 6 / 13 | |
| 4.54.3 | 6 / 13 | |
| 4.54.2 | 6 / 13 | |
| 4.54.1 | 6 / 13 | |
| 4.53.5 | 6 / 13 | |
| 4.53.4 | 6 / 13 | |
| 4.53.3 | 6 / 13 | |
| 4.53.2 | 6 / 13 | |
| 4.53.1 | 6 / 13 | |
| 4.53.0 | 6 / 13 | |
| 4.51.0 | 6 / 13 | |
| 4.50.1 | 6 / 13 | |
| 4.50.0 | 6 / 13 | |
| 4.49.3 | 6 / 13 | |
| 4.49.2 | 6 / 13 | |
| 4.49.1 | 6 / 13 | |
| 4.49.0 | 6 / 13 | |
| 4.48.1 | 6 / 13 |
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.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
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-03-17, 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.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 2025-03-13, 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.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.