@heliofi/launchpad-common
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.
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Known maintainer resuming publishing; no malicious payload in diff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer matches existing known name per provenance info. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): buffer is a standard well-known polyfill, not a supply-chain risk. | ai | |
| phantom-deps | phantom-dep:bs58 | AI (phantom-deps): Config-only reference, consistent with monorepo shared package pattern. | ai |
Versions (showing 18 of 118)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 6 / 4 | |
| 1.3.3 | 6 / 4 | |
| 1.3.2 | 6 / 4 | |
| 1.3.1 | 6 / 4 | |
| 1.3.0 | 6 / 4 | |
| 1.2.0 | 6 / 4 | |
| 1.1.7 | 6 / 4 | |
| 1.1.6 | 6 / 4 | |
| 1.1.5 | 6 / 4 | |
| 1.1.4 | 6 / 4 | |
| 1.1.3 | 6 / 4 | |
| 1.1.2 | 6 / 4 | |
| 1.1.1 | 6 / 4 | |
| 1.1.0 | 6 / 4 | |
| 1.0.5 | 6 / 4 | |
| 1.0.4 | 6 / 4 | |
| 1.0.3 | 6 / 4 | |
| 1.0.1 | 5 / 4 |
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.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 (ib1) than the most recent previously approved version (hhenryhharris) on 2024-12-18, but ib1 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.3.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 (hhenryhharris) than the most recent previously approved version (ib1) on 2024-12-17, but hhenryhharris 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.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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 (ib1) than the most recent previously approved version (martinavagyan) on 2024-10-22, but ib1 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.1.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 (ib1) than the most recent previously approved version (martinavagyan) on 2024-10-10, but ib1 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.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.