@studyportals/datalake-event-tracker-dll
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@studyportals/datalake-event-tracker | AI (phantom-deps): DLL bundle pattern — dependency is bundled via webpack, not directly imported in source. Stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 7.10.0 | 1 / 3 | |
| 7.9.0 | 1 / 3 | |
| 7.7.5 | 1 / 3 | |
| 7.7.4 | 1 / 3 | |
| 7.7.3 | 1 / 3 | |
| 7.7.2 | 1 / 3 | |
| 7.5.6 | 1 / 3 | |
| 7.5.5 | 1 / 3 | |
| 7.5.3 | 1 / 3 | |
| 7.5.2 | 1 / 3 | |
| 7.5.1 | 1 / 3 | |
| 7.5.0 | 1 / 3 | |
| 7.4.2 | 1 / 3 | |
| 7.4.0 | 1 / 3 | |
| 7.3.0 | 1 / 3 | |
| 7.2.0 | 1 / 3 | |
| 7.1.0 | 1 / 3 | |
| 7.0.1 | 1 / 3 | |
| 7.0.0 | 1 / 3 |
v7.5.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 (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
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 (fationsh) than the most recent previously approved version (gilalves95) on 2025-03-04, 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.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 (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 findingsPackage 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 (alexandramarginean) 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 findingsPackage 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 (alexandramarginean) 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.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 (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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.