@colijnit/mainapi
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
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 300.1.3 | 3 / 12 | |
| 300.1.2 | 3 / 12 | |
| 300.1.1 | 3 / 12 | |
| 300.1.0 | 3 / 12 | |
| 262.1.13 | 3 / 12 | |
| 262.1.12 | 3 / 12 | |
| 262.1.11 | 3 / 12 | |
| 262.1.10 | 3 / 12 | |
| 262.1.9 | 3 / 12 | |
| 262.1.8 | 3 / 12 | |
| 262.1.7 | 3 / 12 | |
| 262.1.6 | 3 / 12 | |
| 262.1.3 | 3 / 12 | |
| 262.1.1 | 3 / 12 | |
| 262.1.0 | 3 / 12 | |
| 261.1.12 | 3 / 12 | |
| 261.1.11 | 3 / 12 | |
| 261.1.10 | 3 / 12 | |
| 261.1.9 | 3 / 12 | |
| 261.1.0 | 3 / 12 | |
| 260.1.11 | 3 / 12 | |
| 260.1.10 | 3 / 12 | |
| 260.1.9 | 3 / 12 | |
| 260.1.7 | 3 / 12 | |
| 260.1.4 | 3 / 12 | |
| 260.1.3 | 3 / 12 |
v300.1.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 (jilliscit) than the most recent previously approved version (elske) on 2026-07-27, but jilliscit 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.
v300.1.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 (daan.vdj) than the most recent previously approved version (elske) on 2026-07-17, but daan.vdj 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.
v300.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 (elske) than the most recent previously approved version (ralf.eversen) on 2026-07-15, but elske 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.
v300.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 (ralf.eversen) than the most recent previously approved version (elske) on 2026-07-13, but ralf.eversen 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.
v262.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v262.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v262.1.11
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 (elske) than the most recent previously approved version (daan.vdj) on 2026-07-09, but elske 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.
v262.1.10
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 (daan.vdj) than the most recent previously approved version (patrickvkeulen) on 2026-07-03, but daan.vdj 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.
v262.1.9
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 (patrickvkeulen) than the most recent previously approved version (ralf.eversen) on 2026-06-30, but patrickvkeulen 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.
v261.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v261.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.