@xylabs/set
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Likely CI/CD pipeline change for an established XY Labs package; no other indicators of compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established XY Labs org package with 486 versions and clean publisher history; dormancy likely reflects org release cadence change. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped @xylabs package; Levenshtein match to 'next' is a false positive for this established org. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @xylabs package; Levenshtein match to 'jest' is a false positive for this established org. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @xylabs package; Levenshtein match to 'got' is a false positive for this established org. | ai |
Versions (showing 14 of 119)
| Version | Deps | Published |
|---|---|---|
| 5.0.13 | 0 / 4 | |
| 5.0.12 | 0 / 4 | |
| 5.0.11 | 0 / 4 | |
| 5.0.10 | 0 / 4 | |
| 5.0.9 | 0 / 4 | |
| 5.0.8 | 0 / 4 | |
| 5.0.7 | 0 / 4 | |
| 5.0.6 | 0 / 4 | |
| 5.0.5 | 0 / 4 | |
| 5.0.4 | 0 / 4 | |
| 5.0.3 | 0 / 4 | |
| 5.0.2 | 0 / 4 | |
| 5.0.1 | 0 / 4 | |
| 5.0.0 | 0 / 4 |
v5.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.