@signalk/resources-provider
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
Keywords
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.5.1 | 4 / 1 | |
| 1.5.0 | 4 / 1 | |
| 1.4.1 | 4 / 1 | |
| 1.4.0 | 4 / 1 | |
| 1.3.2 | 4 / 9 | |
| 1.3.1 | 4 / 9 | |
| 1.3.0 | 4 / 10 | |
| 1.2.1 | 4 / 10 | |
| 1.2.0 | 3 / 10 |
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.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 (tkurki) than the most recent previously approved version (panaaj) on 2024-12-28, but tkurki 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.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 (tkurki) than the most recent previously approved version (panaaj) on 2024-11-17, but tkurki 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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.