@datacamp/learn-vm-scripts
Scripts used by VMs in learn.
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:puppeteer-extra | AI (phantom-deps): Used via config/CLI wiring, not direct import; low risk for automation tool. | ai | |
| phantom-deps | phantom-dep:puppeteer-extra-plugin-stealth | AI (phantom-deps): Same pattern as puppeteer-extra; declared for stealth automation plugin. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Config-referenced validation lib, common false positive. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): CLI arg parser referenced in config, common false positive. | ai | |
| phantom-deps | phantom-dep:puppeteer-core | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-prettier | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.14.2 | 5 / 15 | |
| 1.14.1 | 5 / 15 | |
| 1.14.0 | 5 / 15 | |
| 1.13.8 | 5 / 15 | |
| 1.13.7 | 5 / 15 | |
| 1.13.6 | 5 / 15 | |
| 1.13.5 | 7 / 17 | |
| 1.8.6 | 7 / 18 | |
| 1.3.1 | 5 / 18 | |
| 1.3.0 | 5 / 18 | |
| 1.2.5 | 5 / 18 | |
| 1.2.2 | 5 / 18 | |
| 1.2.1 | 5 / 18 |
v1.8.6
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: datacamp-machine-user.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (datacamp-machine-user) than the most recent previously approved version (_bogdan_floris_) on 2025-11-05, but datacamp-machine-user 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.
v1.2.5
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 (_bogdan_floris_) than the most recent previously approved version (ewaldbervoets) on 2025-05-02, but _bogdan_floris_ 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.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.