@tinkoff/terminus
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 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.6.1 | 2 / 5 | |
| 0.5.5 | 2 / 5 | |
| 0.5.4 | 2 / 5 | |
| 0.5.3 | 2 / 5 | |
| 0.5.2 | 2 / 5 | |
| 0.5.1 | 2 / 6 | |
| 0.4.7 | 2 / 6 | |
| 0.4.6 | 2 / 6 | |
| 0.4.5 | 2 / 6 | |
| 0.4.4 | 2 / 6 | |
| 0.4.3 | 2 / 6 | |
| 0.4.2 | 2 / 6 | |
| 0.3.4 | 2 / 6 | |
| 0.3.3 | 2 / 6 | |
| 0.3.1 | 2 / 6 | |
| 0.2.1 | 2 / 6 | |
| 0.2.0 | 2 / 6 | |
| 0.1.9 | 2 / 6 | |
| 0.1.8 | 2 / 6 | |
| 0.1.7 | 2 / 6 | |
| 0.1.6 | 2 / 6 | |
| 0.1.5 | 2 / 6 | |
| 0.1.4 | 2 / 6 | |
| 0.1.3 | 2 / 6 | |
| 0.1.2 | 2 / 6 | |
| 0.0.5 | 2 / 6 | |
| 0.0.4 | 2 / 6 | |
| 0.0.3 | 2 / 6 | |
| 0.0.2 | 2 / 6 | |
| 0.0.1 | 2 / 6 |
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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 (super_oleg) than the most recent previously approved version (tinkoffbank) on 2023-10-23, but super_oleg 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.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.