@studyportals/datalake-event-tracker
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Org-published package with consistent release history; lack of Sigstore attestation is not a risk signal here. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 7.10.0 | 1 / 12 | |
| 7.8.0 | 1 / 12 | |
| 7.7.5 | 1 / 12 | |
| 7.7.4 | 1 / 12 | |
| 7.7.3 | 1 / 12 | |
| 7.7.2 | 1 / 12 | |
| 7.7.0 | 1 / 12 | |
| 7.5.5 | 1 / 12 | |
| 7.5.3 | 1 / 12 | |
| 7.5.2 | 1 / 12 | |
| 7.5.1 | 1 / 12 | |
| 7.5.0 | 1 / 12 | |
| 7.4.2 | 1 / 12 | |
| 7.4.1 | 1 / 12 | |
| 7.4.0 | 1 / 12 | |
| 7.3.0 | 1 / 12 | |
| 7.2.0 | 1 / 12 | |
| 7.1.0 | 1 / 12 | |
| 7.0.1 | 1 / 12 | |
| 7.0.0 | 1 / 12 |
v7.5.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (orlandoliccardo) than the most recent previously approved version (fationsh) on 2025-04-02, but orlandoliccardo 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.
v7.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (fationsh) than the most recent previously approved version (gilalves95) on 2025-03-03, but fationsh 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.
v7.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gilalves95) than the most recent previously approved version (orlandoliccardo) on 2025-02-25, but gilalves95 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.
v7.4.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (fationsh) than the most recent previously approved version (orlandoliccardo) on 2025-02-21, but fationsh 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.
v7.4.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (orlandoliccardo) than the most recent previously approved version (gilalves95) on 2025-01-28, but orlandoliccardo 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.
v7.4.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexandramarginean) than the most recent previously approved version (gilalves95) on 2024-12-18, but alexandramarginean 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.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.