@ifc-lite/mutations
Mutation tracking and property editing for IFC-Lite
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ifc-lite/parser | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic fires as false positive for intra-workspace deps. | ai | |
| provenance | no-provenance | AI (provenance): Young monorepo package; provenance not yet configured but no other risk signals present. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 1 / 2 | |
| 1.14.5 | 1 / 2 | |
| 1.14.4 | 1 / 2 | |
| 1.14.3 | 1 / 2 | |
| 1.14.2 | 2 / 2 | |
| 1.14.1 | 2 / 2 | |
| 1.14.0 | 2 / 2 | |
| 1.13.0 | 2 / 2 | |
| 1.11.5 | 2 / 2 | |
| 1.11.4 | 2 / 2 | |
| 1.11.3 | 2 / 2 | |
| 1.11.2 | 2 / 2 | |
| 1.11.1 | 2 / 2 | |
| 1.11.0 | 2 / 2 | |
| 1.10.0 | 2 / 2 | |
| 1.9.0 | 2 / 2 | |
| 1.8.0 | 2 / 2 | |
| 1.7.0 | 2 / 2 | |
| 1.6.1 | 2 / 2 | |
| 1.6.0 | 2 / 2 | |
| 1.5.0 | 2 / 2 | |
| 1.4.0 | 2 / 2 |
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.