@newskit-render/api
helper package for accessing MAIN and NK API data
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @newskit-render/api; 432 versions, 1633 days old. Not a typosquat of hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package with long history; coincidental Levenshtein match, not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package with long history; coincidental Levenshtein match, not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package with long history; coincidental Levenshtein match, not a typosquat of ajv. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql is a direct runtime dependency in package.json; used via @apollo/client peer relationship. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.20.0 | 4 / 22 | |
| 1.11.0 | 4 / 21 | |
| 1.10.0 | 4 / 21 | |
| 1.9.0 | 4 / 20 | |
| 1.8.0 | 4 / 20 | |
| 1.7.0 | 4 / 20 | |
| 1.6.8 | 4 / 20 | |
| 1.6.7 | 4 / 20 | |
| 1.6.6 | 4 / 20 | |
| 1.6.5 | 4 / 20 | |
| 1.6.4 | 4 / 20 | |
| 1.6.3 | 4 / 20 | |
| 1.6.2 | 4 / 20 | |
| 1.6.0 | 4 / 20 | |
| 1.5.6 | 4 / 20 | |
| 1.5.5 | 4 / 20 | |
| 1.5.4 | 4 / 20 | |
| 1.5.3 | 4 / 20 | |
| 1.5.2 | 4 / 20 | |
| 1.5.1 | 4 / 20 | |
| 1.5.0 | 4 / 20 | |
| 1.4.0 | 4 / 20 | |
| 1.3.0 | 4 / 20 | |
| 1.2.2 | 4 / 20 | |
| 1.2.1 | 4 / 20 | |
| 1.2.0 | 4 / 20 | |
| 1.1.0 | 4 / 20 | |
| 1.0.0 | 4 / 20 |
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.